Skip to main content
Glama

Look up tools for AI agents

find_tools
Read-only

The site's directory of tools agents and their builders use: protocols, frameworks, coding agents, MCP servers, browsers, sandboxes, memory, search, evaluation and more. No arguments: the categories. With query, category or speaks: matching tools, each with what it is, its maker and its address. With id: one tool in full, with what an automatic check last found (address answering, latest release, licence). Written by the site, alphabetical, never ranked by popularity.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOne tool, by the id a list gave.
limitNoHow many tools to return (default 50).
queryNoWords to look for; best match first. 2 to 100 characters.
speaksNoOnly tools that support this protocol or standard, such as "mcp" or "a2a".
categoryNoA category slug from the list this tool returns with no arguments, such as "frameworks" or "mcp-servers".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only and open-world access, so the bar is lower, and the description still adds non-obvious behavior: results are 'written by the site, alphabetical, never ranked by popularity,' which forecloses assumptions about relevance ordering. It also discloses what the id mode returns in full, including fields produced by an 'automatic check' (address answering, latest release, licence), which an agent could not infer from annotations. It does not discuss pagination or what happens when a query returns nothing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

About 80 words with no filler, and the arrangement is front-loaded: subject of the directory first, then the three modes in escalating specificity. The clipped, telegraphic clauses ('No arguments: the categories.') are compact but read as fragments, which slightly reduces clarity for little length savings.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry return-value information, and it does so for each mode, including ordering and the provenance-check fields on single-record lookups. With all five parameters documented in the schema and mode behavior covered, an agent can call this correctly; only edge behavior (empty results, behavior of limit versus filtered sets) is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so every parameter's meaning is already documented, and the baseline is 3. The description adds value mainly at the parameter-interaction level — which combinations select which result shape, and that category slugs must be harvested from the argument-free call — plus illustrative example values ('mcp', 'a2a', 'frameworks'). It adds little about individual parameter syntax beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete resource — a directory of tools (protocols, frameworks, agent runtimes, MCP servers, etc.) — and enumerates the three result modes: categories with no arguments, matching tools with query/category/speaks, and a single full record with id. It is clearly not one of the sibling get_/list_/search_ tools, which target problems, topics, and requests. The only weakness is that the opening sentence describes content rather than leading with a verb, so the operational purpose emerges in the second sentence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is spelled out per argument combination: no arguments to get the category list, query/category/speaks to get a filtered list, id to get one record in full. It also implies the correct call order by noting that category takes 'a category slug from the list this tool returns with no arguments.' It stops short of naming alternatives or stating when not to use the tool, which keeps it off a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources