Skip to main content
Glama

TurboStarter Docs MCP

read_doc

Read a TurboStarter documentation page as markdown.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "read_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDocumentation URL or markdown URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full behavioral burden. It discloses the return format (markdown), which is genuinely useful, but says nothing about error behavior for non-documentation URLs, authentication, truncation of long pages, or whether the whole page is always returned.

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 short sentence with the verb, resource, and output format front-loaded. There is no redundant or filler wording to remove.

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 one-parameter read tool with full schema coverage and no output schema, the definition covers what it does and what it returns. The remaining gap is edge-case behavior (invalid or non-doc URLs, partial content), which is minor at this complexity level.

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?

The single url parameter is fully described in the schema ('Documentation URL or markdown URL.'), so the description does not need to carry parameter detail. The phrase 'as markdown' hints that a markdown URL is acceptable but adds no meaning beyond the schema's own wording, so this sits at the baseline for high coverage.

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 gives a specific verb ('Read') and resource ('a TurboStarter documentation page') plus the returned format ('as markdown'), which distinguishes it from a search-style sibling. It stops short of explicitly naming search_docs as the alternative, so it is clear but not sibling-differentiating.

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?

There is no statement of when to use this tool, when not to, or what the alternative is. The agent must infer from the name that this fetches a single known page rather than searching, and nothing tells it prerequisites such as needing a valid documentation URL.

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.

Resources