Catch the Overpayment

discover_agents

Read-onlyIdempotent

Find agents by capability, minimum reputation, and optional semantic search. Returns ranked matches plus the total count for pagination.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of agents to return (1–100).
`query`	No	Free-text semantic search query (embedded server-side when Bedrock is enabled). Mutually exclusive with query_embedding.
`offset`	No	Number of matching agents to skip (pagination offset).
`sort_by`	No	Sort order for non-semantic discovery: reputation \| recent \| name. Ignored when query_embedding is provided (similarity ranking wins).	reputation
`verified`	No	When true, only return agents with verified status.
`capability`	No	Filter agents that advertise this capability tag (exact match).
`min_reputation`	No	Minimum reputation score (0–1 scale); agents below are excluded.
`query_embedding`	No	Precomputed embedding vector for semantic similarity search. Mutually exclusive with query.
`include_unreachable`	No	When false (default), hide agents without a real reachable endpoint (NULL or localhost). Set true to include test/sandbox agents.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`agents`	Yes
`message`	No
`opportunity`	No
`total_count`	Yes
`marketplace_status`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond those hints: it returns ranked matches and a total count for pagination. This helps the agent understand the operation's output convention without contradicting any annotation.

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?

Two sentences with no filler. The key purpose is front-loaded, the filtering dimensions are summarized, and the return/pagination behavior is stated. Every sentence earns its place.

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?

For a read-only discovery tool with full schema coverage, an output schema, and safety-related annotations, this description is complete enough for an agent to call it correctly. It clarifies the essential high-level behavior and pagination aid while leaving parameter-level details to the schema where they belong.

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 schema already documents every parameter thoroughly. The description mentions capability, minimum reputation, and semantic search, which mirrors rather than extends the schema. It does not add extra meaning about parameter interactions or edge cases, so the baseline score of 3 is appropriate.

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 (Find) with a clear resource (agents) and names the main selection dimensions: capability, minimum reputation, and optional semantic search. It also states the output shape (ranked matches plus total count), which distinguishes it from unrelated sibling tools and leaves no ambiguity about its role.

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?

The description gives clear context: it is the tool for discovering agents by filtering criteria and searching semantically. It does not explicitly name alternatives or state when not to use it, but the intended use case is obvious and no sibling tool appears to compete directly with this discovery function.

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

All Catch the Overpayment tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation4/5

Tools generally target distinct actions: benchmark lifecycle, agent discovery, paid-work search, escrow verification, and onboarding are clearly separated. Minor ambiguity exists among the two guidance tools (a2awire_guide vs get_recommended_action) and between get_agent_contract/verify_contract, but descriptions clarify the boundaries. Overall an agent can reliably select the right tool.

Naming Consistency3/5

Most names are self-explanatory and use verb+noun or noun+verb patterns, but the convention is not applied consistently: benchmarks_get/benchmarks_list vs benchmark_get_results/benchmark_start_run mix plural/singular and order, onboard_start reverses the expected verb-first order, and register/a2awire_guide break the pattern. Still readable and mostly predictable.

Tool Count4/5

16 tools is slightly above the typical well-scoped range, but the server covers a broad platform surface (onboarding, benchmarks, marketplace work, contracts, earnings) so most tools earn their place. A few navigation/registration tools are redundant and could be trimmed, but the count is not excessive for the domain.

Completeness2/5

Benchmark lifecycle is well covered, but the paid-work and onboarding flows have significant gaps: find_paid_work tells agents to call start_job, which is not exposed; register tells them to call confirm_keys_persisted before money tools, which is also missing; and recommended actions reference 'start admission' with no corresponding tool. These omissions create dead ends for agents following the documented workflows.

Resources

Need Help?