Skip to main content
Glama
mapbox

Mapbox MCP Server

Official

Category Search Tool

category_search_tool
Read-onlyIdempotent

Find all places matching a specified category (e.g., restaurant, hotel) using Mapbox. Supports proximity bias and bounding box filters.

Instructions

Return all places that match a category (industry, amenity, or NAICS‑style code). Use when the user asks for a type of place, plural or generic terms like 'museums', 'coffee shops', 'electric‑vehicle chargers', or when the query includes is‑a phrases such as 'any', 'all', 'nearby'. Do not use when a unique name or brand is provided. Supports both JSON and text output formats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bboxNoBounding box to limit results within specified bounds
limitNoMaximum number of results to return (1-25)
formatNoOutput format: "json_string" returns raw GeoJSON data as a JSON string that can be parsed; "formatted_text" returns human-readable text with place names, addresses, and coordinates. Both return as text content but json_string contains parseable JSON data while formatted_text is for display.formatted_text
countryNoArray of ISO 3166 alpha 2 country codes to limit results
categoryYesThe canonical place category name to search for (e.g., "restaurant", "hotel", "cafe"). To get the full list of supported categories, use the category_list_tool.
languageNoIETF language tag for the response (e.g., "en", "es", "fr", "de", "ja")
proximityNoLocation to bias results towards as {longitude, latitude}. If not provided, defaults to IP-based location.
poi_category_exclusionsNoArray of POI categories to exclude from results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
featuresYes
attributionYes
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive. Description adds that it returns places, supports JSON and text output, and mentions category types, providing useful behavioral context without contradicting annotations.

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 concise sentences with front-loaded purpose, efficient and no wasted words.

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?

With 100% schema coverage, annotations, and an output schema, the description covers purpose, usage guidance, and output formats adequately. Lacks pagination details but limit parameter is clear. Generally complete for 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 the schema fully documents all 8 parameters. The description only restates output format options, adding no new parameter semantics beyond what's already in the schema.

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?

Description clearly states the tool returns places by category, specifies types of categories (industry, amenity, NAICS), and provides usage examples that distinguish it from sibling tools like search_and_geocode_tool by instructing not to use when a unique name is given.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (generic terms, plural, 'any', 'all', 'nearby') and when not to use (unique name or brand), offering clear decision criteria for the agent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mapbox/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server