Skip to main content
Glama

Mapbox

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedInput schema / properties / description
      {
  "description": "Alias for query.",
  "type": "string"
}
    • addedInput schema / properties / q
      {
  "description": "Alias for query.",
  "type": "string"
}
    • changedInput schema / properties / query / description
      Before
      "Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\")"
      After
      "Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\"). Accepts task, q, description, search as aliases."
    • addedInput schema / properties / search
      {
  "description": "Alias for query.",
  "type": "string"
}
    • addedInput schema / properties / task
      {
  "description": "Alias for query.",
  "type": "string"
}
  2. Changed1 schema field changed
    • addedInput schema / examples
      [
  {
    "query": "look up FDA drug approvals"
  },
  {
    "query": "analyze housing market trends"
  }
]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already cover read-only/idempotent/non-destructive traits. The description adds valuable behavioral details: returns top-N tools with full input schemas and 'ready to call directly, no second schema lookup needed.' This goes beyond the annotations to explain the exact output wrapper. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and usage context. The long list of covered domains earns its place by setting expectations for the tool's scope, though it could be trimmed slightly without losing meaning. Overall efficient for the information it conveys.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a straightforward discovery tool with no output schema, the description is complete. It explains the return format (names, descriptions, schemas) and the intended first-call pattern. Combined with the comprehensive schema and annotations, the agent has everything needed to select and invoke this tool.

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 all six parameters (query and its aliases, limit) are already adequately described. The description does not add any parameter-specific semantics beyond what the schema provides, so the baseline of 3 applies.

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 opens with 'Find tools by describing the data or task,' which clearly states the verb and resource. It distinctively frames the tool as a discovery/browsing utility, and the phrase 'Call this FIRST when you have many tools available' helps distinguish it from sibling tools that answer directly.

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?

It provides explicit usage context: 'Use when you need to browse, search, look up, or discover what tools exist' and 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' This is strong guidance, though it does not explicitly name alternative tools or state when not to use it beyond the 'not just one answer' clue.

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

All Mapbox toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Many tools have overlapping purposes (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim) and several tools serve similar data-retrieval functions, making it difficult for an agent to distinguish which to use.

Naming Consistency4/5

Tool names mostly follow a consistent verb_noun pattern (e.g., geocode_forward, generate_llms_txt, resolve_entity). A few less descriptive names (forget, recall) exist but overall naming is predictable.

Tool Count2/5

38 tools is far too many for a server branded as 'Mapbox'. Only about 8 tools directly relate to map/geospatial functionality; the rest are unrelated (Pipeworx data, Polymarket, memory). The scope is dramatically overextended.

Completeness2/5

The Mapbox-specific tools lack coverage of major features like style management, tilesets, or data upload. The non-Mapbox tools cover their domains moderately, but the server's overall completeness for its named purpose (Mapbox) is severely lacking.

Resources