Skip to main content
Glama

Search Live Audited Agent Directory

search_agent_directory
Read-onlyIdempotent

Browse and filter the audited Radial Switchboard phonebook by keyword substring and Virginia Scout health grade without consuming matchmaking call quota. Use when exploring catalog coverage by name, vendor, or grade; use matchmake_agent_crew instead when ranking capability-matched finalists for execution.

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": "search_agent_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of directory records to return (1..50, default 20).
queryNoOptional case-insensitive keyword filter matched against agent_id, name, description, and endpoint URL.
grade_filterNoFilter by Virginia Scout audit grade ('AB' live <=350ms default, 'A' <=150ms, 'B' <=350ms, 'C' <=700ms, 'D' offline code, 'ALL' every non-poison record).

Output Schema

NameRequiredDescriptionDefault
agentsYesMatching directory records with grade, coupler, and endpoint metadata.
returned_countYesNumber of records included in agents.
total_matchingYesTotal phonebook records matching the filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is read-only, idempotent, closed-world, and non-destructive. The description adds meaningful behavior beyond those annotations by noting the directory is audited and that searches do not consume matchmaking call quota, though it does not discuss pagination or return-shape details.

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?

The description is two compact sentences with no wasted wording. Purpose and scope come first, followed by the explicit alternative and usage condition.

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

Completeness5/5

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

Given the full schema, rich annotations, and presence of an output schema, the description contains the information an agent needs: what the tool searches, how to filter, when to use it, when to use a sibling, and the quota-related behavior.

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 description coverage is 100%, so the baseline is 3 even without additional parameter explanation in the description. The description reinforces keyword substring and health-grade filtering but adds little syntax, default, or matching-detail meaning beyond what the schema already provides.

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

Purpose5/5

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

The description uses a specific verb pair (browse and filter) and names the resource as the audited Radial Switchboard phonebook. It also explicitly distinguishes this catalog search from matchmake_agent_crew, so an agent can select it without needing to infer sibling behavior.

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

Usage Guidelines5/5

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

It states when to use this tool: exploring catalog coverage by name, vendor, or grade. It also names the alternative matchmake_agent_crew and specifies that alternative's purpose: ranking capability-matched finalists for execution.

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.