Skip to main content
Glama

Search the docs

search_docs
Read-onlyIdempotent

Search RentADriver's published documentation (API, MCP tools, pricing, coverage, integrations, answers, FAQ). Returns titles, absolute URLs to cite and a snippet; read a page with read_docs_page.

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
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral context beyond them: what comes back (titles, absolute URLs suitable for citation, and a snippet), which tells the agent the result is a citation-ready index rather than page bodies.

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?

Two sentences, no filler: scope first, return shape second, next-step pointer last. Every clause carries information an agent needs and nothing is repeated from the annotations or schema.

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?

An output schema exists, so return values need not be spelled out, and the description nonetheless previews them briefly. For a simple two-parameter read tool this is nearly complete; the only material gap is the absence of any guidance on query formulation and the limit parameter's trade-off.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for both parameters, yet it says nothing about how the query is interpreted (keyword vs. natural language, supported syntax) or what limit controls beyond the schema's numeric bounds. Neither parameter gains any meaning from the description text.

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 names a specific verb (search) and a specific resource (RentADriver's published documentation), then enumerates the covered content areas (API, MCP tools, pricing, coverage, integrations, answers, FAQ). It is clearly distinguishable from read_docs_page, which is described as the follow-up for reading an individual page.

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 states the tool's role in a two-step workflow and explicitly routes to read_docs_page for full-page content, which is the key alternative an agent needs. It stops short of stating when NOT to use this search (e.g., use get_faq or get_pricing for structured lookups), so it falls short of full 5-level 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.