stats
High-level stats about the directory: total services, healthy count, sources.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
agent-tools (x402 + MCP + A2A directory)
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should cover behavioral traits. It only states what the tool returns without mentioning side effects, permissions, or limits. The tool likely read-only but not stated.
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?
Single sentence, no redundancy, front-loaded with key information. Every word contributes to the purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and an output schema, the description covers the basics. However, it could elaborate on what 'sources' means or provide examples of returned data to aid agent understanding.
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?
No parameters, so the description doesn't need to explain them. Schema coverage is 100% (nonexistent), meeting the baseline. The description is clear enough for a parameterless tool.
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 specifies it provides high-level stats (total services, healthy count, sources), clearly differentiating from sibling tools like search or get that return individual items. However, it could be more concrete about the exact metrics.
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?
No guidance on when to use this tool versus alternatives like search or list_categories. The description implies it's for aggregate overviews, but lacks explicit context about appropriate use cases or prerequisites.
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.
TDQS
A3.8/5.0
Disambiguation4/5
Tools are mostly distinct with clear purposes. However, 'search', 'search_mcp_servers', 'search_a2a_agents', 'search_resources', and 'ask_services' have overlapping discovery functions, though descriptions differentiate them (e.g., LLM ranking vs deterministic). This could slightly confuse an agent.
Naming Consistency3/5
Naming conventions are mixed: some follow 'verb_noun' (e.g., ask_services, list_categories), some are single verbs (get, register, search, stats), and some use underscores (search_a2a_agents, search_mcp_servers). The pattern is not fully consistent but remains readable.
Tool Count5/5
11 tools is well within the recommended 3-15 range for a directory server covering x402, MCP, and A2A services. Each tool serves a distinct purpose without bloat.
Completeness4/5
The toolset covers core directory operations: discovery (multiple search variants), details, registration, safety scanning, and stats. Missing update/delete for services is a minor gap but not critical for basic usage.