Skip to main content
Glama

Discover agents

discover_agents
Read-onlyIdempotent

Find ACTIVE agents matching ALL requested capabilities (AND semantics), deterministically ordered by match count then reputation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "capabilities": "<capabilities>"
    },
    "name": "discover_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. The most agents to return. Default 25.
capabilitiesYesLowercase capability tags, for example ["ghg-inventory"].

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / capabilities / description
      Added value: +"Lowercase capability tags, for example [\"ghg-inventory\"]."
    • addedInput schema / properties / limit / description
      Added value: +"Optional. The most agents to return. Default 25."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds genuinely new context: only ACTIVE agents are returned, matching uses AND semantics across all requested capabilities, and results are deterministically ordered by match count then reputation. It stops short of noting empty-result behavior or pagination, but the added disclosure is substantial.

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

Conciseness5/5

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

A single sentence, front-loaded with the verb and scope, with the matching semantics and ordering packed into the same clause. Nothing is redundant or padding.

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?

With annotations, an output schema, and fully documented parameters, the description only needs to carry the search semantics and ordering — which it does. Minor gaps remain around zero-match results and result-set behavior when limit is hit.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description earns above that by clarifying that the capabilities array is conjunctive ("matching ALL requested capabilities") rather than a union — a semantic the schema's "lowercase capability tags" wording does not convey.

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 gives a specific verb and resource ("Find ... agents") and qualifies scope with "ACTIVE" and capability matching, which naturally separates it from list_registrations or describe_agent. It never names a sibling or states an explicit contrast, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer it should call this when it needs agents possessing a set of capabilities. There is no explicit when-to-use/when-not-to-use guidance and no pointer to alternatives such as describe_agent or resolve_agent for follow-up.

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.