get_all_docs
Retrieve every document in the Forkast documentation space
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
forkast-mcp-docs
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds useful scope ('Forkast documentation space') but does not disclose potential behaviors like result size, pagination, or performance characteristics. This is minimal but non-zero context.
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 a single sentence with no redundant words. It front-loads the action ('Retrieve') and is perfectly sized for the tool's simplicity.
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 tool with no parameters, no annotations, and no output schema, the description adequately states what it does and its scope. There are no hidden complexities or missing contextual elements that would require elaboration.
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?
The tool has zero parameters, so the schema is trivially covered (100%). Per the rubric, 0 parameters earns a baseline of 4. The description adds no parameter details, but none are needed.
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 the specific verb 'Retrieve' and clearly identifies the resource ('every document in the Forkast documentation space'). This distinguishes it from sibling tools like get_doc (specific document) and search_query/search_title (search functionality), making the purpose unambiguous.
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 clearly implies this tool is for bulk retrieval, but it does not explicitly state when to use it over alternatives or when not to use it. The sibling tool names offer implicit contrast, but the description itself lacks explicit usage guidance.
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.9/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: retrieving all docs, retrieving one by ID, searching full-text, and searching by title. There is minimal overlap between search_query and search_title, but the descriptions make the distinction clear.
Naming Consistency4/5
The names follow a verb-first pattern (get_all_docs, get_doc, search_query, search_title), but they are not perfectly uniform: get_all_docs and get_doc use object-oriented names, while search_query and search_title use parameter-oriented names. The inconsistency is minor and does not hinder readability.
Tool Count5/5
With 4 tools, the server is well-scoped for documentation retrieval. The count is within the ideal range and each tool serves a distinct core function without unnecessary redundancy.
Completeness5/5
The server covers the essential read-only operations for documentation: fetching all docs, retrieving one, full-text search, and title-based search. No critical gaps are apparent for a documentation retrieval use case.