search_query
Full-text search across Forkast documentation content
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query text |
forkast-mcp-docs
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavior. It only states 'full-text search' without mentioning whether it is read-only, what it returns, pagination, or any access restrictions. The read-only nature is implied by 'search' but not explicitly stated, and no additional behavioral context is given. Minimal transparency.
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?
One concise sentence with no filler. All words contribute meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter search tool, the description gives the essential purpose and scope. However, it does not describe the return format or explicitly contrast with search_title, leaving an ambiguity about exact behavior. Overall adequate.
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% (query: 'Search query text'). The tool description adds little beyond that, though the phrase 'full-text' clarifies that the query is matched against document content. Baseline 3 applies.
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?
Description clearly states a specific action (full-text search) and target resource (Forkast documentation content). The qualifier 'full-text' distinguishes it from sibling search_title, which likely searches only titles. High clarity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool vs alternatives. The description implies usage for searching documentation content, but does not mention when not to use it or name search_title as an alternative for title-only searches. Only implied usage.
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.