Skip to main content
Glama

TurboStarter Docs MCP

search_docs

Search TurboStarter documentation across every product. Returns ranked hits with URLs and snippets. Prefer short queries of 2-5 words for one concept; long keyword dumps often return no results.

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": {
      "query": "<query>"
    },
    "name": "search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
queryYesShort search query of 2-5 words for one concept (e.g. 'dark mode', 'billing stripe'). Do not stuff synonyms or the full question into one query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral disclosure burden and does well for a simple search tool: it states the search scope ('across every product'), the return format ('ranked hits with URLs and snippets'), and a failure mode ('long keyword dumps often return no results'). It omits details such as authentication, rate limits, or pagination behavior, but those are less critical here.

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 three tight sentences with no wasted wording. Purpose, return format, and query guidance are front-loaded in a logical order.

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 two-parameter search tool with no annotations or output schema, the description covers what it does, what it returns, and how to phrase queries. Its main gap is the absence of explicit routing guidance versus the read_doc sibling.

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%, so the schema already documents both the query and limit parameters. The description largely repeats the query guidance already present in the schema and does not explain the limit parameter; the added note about long keyword dumps failing is mildly useful but does not materially deepen parameter semantics.

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 states a specific verb and resource: 'Search TurboStarter documentation across every product.' This is clear and actionable, but it does not explicitly distinguish the tool from the sibling read_doc or explain when to search versus read a specific document.

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?

It gives useful query-formulation guidance ('Prefer short queries of 2-5 words for one concept; long keyword dumps often return no results'), but that is parameter usage rather than tool-selection guidance. It does not state when to use search_docs instead of read_doc or mention any 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.

Resources