list-apis
Read-onlyIdempotent
Lists available APIs with their context and purpose
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number | |
| limit | No | Number of APIs per page. Default is 300 | |
| filter | No | API name (or part of it) |
Final POS Docs
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to reiterate safety. The description adds no behavioral details beyond 'lists', but does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, concise, and front-loaded with the key action. No wasted words, but could be more structured for readability.
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?
No output schema is provided, so the description should clarify what is returned. 'With their context and purpose' is too vague. Lacks details on pagination, fields, or how results are structured.
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 coverage is 100% with descriptions for all three parameters. The description adds no additional parameter semantics beyond what the schema provides, so baseline 3 is appropriate.
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 'Lists available APIs with their context and purpose' clearly indicates the tool's verb and resource. It distinguishes from sibling tools like 'get-endpoints' which focus on endpoints rather than APIs themselves. However, 'context and purpose' is slightly vague.
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 such as 'search' or 'get-full-api-description'. The description does not mention use cases or exclusions.
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.7/5.0
Disambiguation5/5
Each tool targets a distinct aspect of API documentation: listing APIs, retrieving endpoints, endpoint details, full description, security schemes, and search. No functional overlap.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern (list-apis, get-endpoints, etc.), but 'search' is a single verb, slightly breaking the pattern. Overall naming is clear and predictable.
Tool Count5/5
With 6 tools, the server is well-scoped for its purpose—comprehensive enough without being overwhelming. The number is appropriate for a documentation explorer.
Completeness4/5
The set covers listing APIs, endpoint details, full spec, security, and search. Minor gaps like endpoint filtering or version comparison exist, but core workflows are well-covered.