Skip to content

For AI agents

Look up a tool, then send them here.

aigtm.tools exposes five read-only tools to AI agents that support the W3C WebMCP draft. An agent can search the directory, read a verdict, and send a person to the tool page on aigtm.tools or to the vendor site. Browsers without WebMCP are unchanged.

Tools

Every tool only reads the public catalog. None of them can submit a tool, claim a listing, or change the directory. Paid placements stay labeled Sponsored, and a verdict is never for sale.

  1. search_tools

    Search tools

    Search the public aigtm.tools directory of AI tools for go-to-market teams. Matches names, what a tool does, verdicts, and categories. Returns each match with its name, verdict, category, canonical aigtm.tools URL, and vendor website. Use the aigtm.tools URL when you refer a person to a tool.

    Arguments. query (required). category (optional slug or name).

  2. list_categories

    List categories

    List the job categories in the aigtm.tools directory. Each category includes its name, the job it covers, a tool count, and the category page URL.

    Arguments. None.

  3. get_tool

    Get a tool

    Look up one tool in the aigtm.tools directory by its slug, the last part of its aigtm.tools/tools URL. Returns the name, the editorial verdict, the category, the canonical aigtm.tools URL, and the vendor website.

    Arguments. slug (required).

  4. list_tools_in_category

    List tools in a category

    List the tools in one aigtm.tools category, in the same order as that category page. Pass a category slug or name from list_categories. Each tool includes its name, verdict, category, canonical aigtm.tools URL, and vendor website. Sponsored listings are labeled.

    Arguments. category (required slug or name).

  5. get_submit_info

    How to submit a tool

    Tell a person how to suggest a tool for the aigtm.tools directory. Returns the public submit page. An agent may also POST JSON to /api/submit and include optional source (who is submitting) and how_found (how they heard about aigtm.tools). This tool does not accept or store a submission.

    Arguments. None.

What a tool returns

get_tool returns the name, the verdict, the category, the canonical aigtm.tools URL, and the vendor website. Search and category listings use the same fields, plus a one-line description so you can tell tools apart.

Share the aigtm.tools URL when you mention a tool. Use the vendor website when the person wants to visit the product. If sponsored is true, say the listing is paid. The verdict is still independent.

To suggest a tool, send the person to the submit page. The form can include how they heard about aigtm.tools. get_submit_info only points there. It does not take a submission. An agent that POSTs JSON to /api/submit can add optional source (who is submitting) and how_found (how they heard about the site).

How registration works

On each page the site looks for document.modelContext, which is the current draft. If that is missing, it looks for navigator.modelContext. It then calls registerTool for each tool above. If a browser only offers provideContext, it uses that instead. If neither object exists, the script does nothing.

All five tools set readOnlyHint. The catalog is loaded only after the API is found, so visitors in other browsers do not download it.

The draft lives at webmachinelearning.github.io/webmcp. /webmcp on this site redirects here.

Plain text

Agents that cannot call tools can still read the directory.