Skip to main content
Glama

mocop

search_agents

Read-only

Search A2A agents.

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": {
      "query": "<query>"
    },
    "name": "search_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesNatural language or keyword query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without the description. The description adds nothing beyond that — no mention of ranking/relevance behavior, what a match looks like, whether results are paginated or truncated by limit, or what the query is matched against.

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

Conciseness3/5

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

It is a single front-loaded sentence with no wasted words, so nothing is bloated. The problem is under-specification rather than verbosity — conciseness is achieved by omitting nearly all useful content.

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

Completeness2/5

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

With no output schema and no annotations explaining return values, the description is the only place an agent could learn what a result contains, and it says nothing. For a search tool with an undocumented limit and unclear semantics of 'A2A agent', the definition is too thin to invoke confidently.

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

Parameters2/5

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

Schema coverage is only 50%: 'query' is documented as natural language or keyword, but 'limit' (1-25) has no description anywhere. The description contributes zero parameter meaning, so it fails to compensate for the undocumented limit parameter (e.g., defaults, ordering of results).

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

Purpose3/5

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

The description gives a verb (Search) and a resource (A2A agents), so it is not a bare tautology and the resource noun does differentiate it from siblings like search_apis and search_mcp_servers. However, 'A2A agents' is unexplained jargon and the description says nothing about what an agent record contains or what searching yields, leaving the purpose only nominally clear.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when to prefer search_apis, search_capabilities, or search_mcp_servers instead, and no prerequisites or scope constraints. The agent must infer the selection criteria purely from the resource noun.

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