Skip to main content
Glama

BETAP: cultural places and local businesses

Search places

buscar_lugares
Read-only

Search verified museums, libraries and cultural projects (Mexico, US, Canada) by text, type, country or distance. Busca museos, bibliotecas y proyectos culturales verificados por texto, tipo, país o cercanía.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buscar_lugares"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoText in name or city / texto en nombre o ciudad
latNo
lngNo
paisNo
tipoNomuseo = museum, biblioteca = library, proyecto = cultural project
limiteNoMax results, up to 50 / máximo 50
radio_kmNoRadius in km, default 50 / radio en km

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results are 'verified' and limited to three countries, but says nothing about result ordering, pagination, or what happens when lat/lng are supplied without radio_km.

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

Conciseness3/5

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

The English sentence is front-loaded and efficient, but the Spanish sentence is a near-verbatim translation that doubles length without adding information. Intentional bilingualism, yet half the text is redundant from a specification standpoint.

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

Completeness3/5

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

With no output schema and 7 all-optional parameters, the description does not explain the behavior of an empty query, whether it returns all results or none, or the default result cap. Read-only safety is covered by annotations, so the remaining gaps are moderate rather than severe.

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 coverage is 57%, with lat, lng and pais undocumented in the schema. The phrase 'by text, type, country or distance' loosely maps to q, tipo, pais and the lat/lng/radio_km cluster, partially compensating, but it adds no format details such as coordinate pairing requirements or the interaction between radius and distance search.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Search verified museums, libraries and cultural projects') and bounds it geographically (Mexico, US, Canada) and by search facets (text, type, country, distance). That resource type implicitly separates it from buscar_negocios, but it never names the sibling or obtener_lugar explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for cultural-venue lookup rather than business lookup, but there is no statement of when to prefer it over buscar_negocios or when to follow up with obtener_lugar, and no exclusions or preconditions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources