Skip to main content
Glama
Sign In

mcp-docs-server

by io.github.mapbox
OverviewDiscussionsAdmin

Search Mapbox Docs Tool

search_mapbox_docs_tool
Read-onlyIdempotent

Search Mapbox documentation by keyword or natural language query. Searches across API reference, GL JS, Help Center, Style Spec, Studio, Search JS, iOS/Android Maps and Navigation SDKs, and Tilesets. Returns ranked results with titles, URLs, and descriptions. Use get_document_tool to fetch the full content of a result 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_mapbox_docs_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1–20, default 5).
queryYesSearch query for Mapbox documentation (e.g. "add a marker", "camera animation", "geocoding API").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds genuine context beyond that: the corpus searched, ranked ordered results, and the exact fields returned (titles, URLs, descriptions). It stops short of noting ranking behavior or empty-result handling.

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?

Three short sentences, front-loaded with what is searched, then what is returned, then the hand-off to the sibling tool. Every sentence earns its place with no filler or repetition of the title.

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?

No output schema exists, yet the description compensates by naming the returned fields and result ordering. For a two-parameter search tool with full annotation coverage, the only real omission is any note on result ranking or what an empty result set looks like.

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%, with both query and limit fully documented including range and default, so the baseline is 3. The phrase 'keyword or natural language query' adds only marginal meaning over the schema's own example queries ('add a marker', 'camera animation').

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?

States a specific verb (Search) and resource (Mapbox documentation), enumerates the content sources covered (API reference, GL JS, Help Center, Style Spec, SDKs, Tilesets), and names the sibling tool used for the next step. An agent can distinguish it from get_document_tool and batch_get_documents_tool without opening a schema.

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?

Explicitly routes follow-up work: 'Use get_document_tool to fetch the full content of a result page.' That gives a clear when-to-use-next condition. It does not mention batch_get_documents_tool or state when not to search (e.g., when a URL is already known), so it stops just short of full alternative coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-docs-server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources