batch_get_documents_toolFetch the full content of multiple Mapbox documentation pages in a single call (max 20). More efficient than calling get_document_tool multiple times. Returns an array of results — failed pages include an error message rather than failing the whole batch.
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | Array of Mapbox documentation page URLs to fetch (max 20). All must be mapbox.com URLs. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds valuable behavioral context beyond the annotations by disclosing the return array structure and that failed pages include an error message rather than failing the whole batch. Annotations already cover read-only, idempotent, and non-destructive traits, so the description supplements rather than repeats them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences long, front-loaded with the core purpose, and each sentence adds distinct value: what it does, why it is better than the alternative, and the partial-failure behavior. No filler or redundant phrases.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter tool with no output schema, the description covers the essential details: action, resource, upper limit, efficiency benefit, and return structure. Combined with the schema and annotations, the agent has enough context to select and invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides 100% coverage of the single 'urls' parameter, including its type, max/min items, format, and the constraint that all URLs must be mapbox.com. The description does not add additional parameter-specific meaning beyond restating the batch context.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches full content of multiple Mapbox documentation pages in a single call, with a specific verb ('Fetch') and resource ('multiple Mapbox documentation pages'). It explicitly distinguishes itself from the sibling get_document_tool by highlighting batch efficiency.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear usage context by naming get_document_tool as the alternative and explaining that this batch version is more efficient for multiple pages. It does not explicitly state when not to use it, but the comparison implies single-page calls should use get_document_tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, non-overlapping purpose: search finds documents, get fetches a single document, and batch fetches multiple documents at once. There is no ambiguity about which tool to use for a given task.
All tools follow a consistent verb_noun_tool pattern: search_mapbox_docs_tool, get_document_tool, batch_get_documents_tool. The naming clearly reflects the action and resource, and the _tool suffix is uniform.
Three tools is an ideal scope for a documentation server: one for searching, one for retrieving individual pages, and one for batched retrieval. Each tool serves a distinct need without redundancy or bloat.
The tool set covers the complete documentation workflow: discover via search, retrieve a single page, and retrieve multiple pages efficiently. There are no obvious missing operations for the stated purpose of accessing Mapbox documentation.