Skip to main content
Glama

brave

by ai.smithery
OverviewDiscussionsAdmin

Place search (POIs, cities, addresses, streets)

brave_place_search
Read-only

Searches Brave's Place Search API. A single call may populate any combination of results (POIs), cities, addresses, streets, and location (the resolved search area), depending on the query shape. Use for POIs near coordinates or a named area, browsing general POIs (omit query, supply coords or location), disambiguating bare city names, resolving specific addresses, or looking up streets. Anchor via latitude+longitude or location; with neither, query is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results (max 50, default 20).
queryNoQuery string. Shape influences the response: POI-like queries return `results`; ambiguous city names return `cities`; address-/street-shaped queries with a geographic anchor return `addresses` and/or `streets`. Omit to browse general POIs in the supplied area. Required if neither `latitude`+`longitude` nor `location` is provided.
unitsNoUnits of measurement for distance values.
geolocNoOptional geolocation token used to refine results.
radiusNoBias toward results closer to the supplied coordinates, in meters. NOT a hard cutoff.
countryNo2-letter country code (ISO 3166-1 alpha-2). Defaults to US.
ui_langNoUser interface language for the response, in the form <lang>-<country> (e.g. en-US).
latitudeNoLatitude of the geographical coordinates to search around (-90 to 90). Typically paired with `longitude`.
locationNoLocation string used as an alternative to lat/long. US: '<city> <state> <country>' (e.g. 'san francisco ca united states'). Non-US: '<city> <country>' (e.g. 'tokyo japan'). Capitalization and commas don't matter.
longitudeNoLongitude of the geographical coordinates to search around (-180 to 180). Typically paired with `latitude`.
safesearchNoFilter level for adult content.
spellcheckNoWhether to spellcheck the query.
search_langNo2-letter language code for the search. Defaults to en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate read-only, non-destructive, open-world behavior. The description adds that the response shape varies by query, which complements annotations without contradiction.

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?

The description is a single paragraph with no redundancy. Each sentence adds meaningful information, front-loading the tool's purpose and key usage patterns.

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?

Given the tool's complexity (13 parameters, no output schema), the description covers the essential interplay between parameters and response types. It could briefly mention ordering or pagination, but is largely sufficient.

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

Parameters4/5

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

All parameters have schema descriptions (100% coverage). The description adds value by explaining the role of 'query' in shaping the response and providing format examples for 'location', going beyond the raw 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?

The description clearly states it searches Brave's Place Search API for POIs, cities, addresses, streets, and locations. It lists specific response components and use cases, distinguishing it from sibling tools that handle images, news, videos, etc.

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 explains when to use the tool for various geospatial queries (POIs, addresses, city disambiguation) and how to anchor searches via coordinates or location. While it doesn't explicitly exclude other tools, the context is clear enough for an agent to decide.

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

All brave 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