Skip to main content
Glama

Directorio Systema

by app.scalesystema
OverviewDiscussionsAdmin

Buscar negocios / Search businesses

buscar_negocios

ES: Busca negocios del directorio público (Miami–Centroamérica) por ubicación {lat,lng}, ciudad, categoría o texto libre. Con ubicación o ciudad busca en un radio dinámico (5 a 50 millas) alrededor de ese punto y lo informa en "alcance". Sin ubicación ni ciudad devuelve el listado por país/global. / EN: Search the public business directory (Miami–Central America) by location {lat,lng}, city, category or free text. With a location or city it searches a dynamic radius (5 to 50 miles) around that point and reports it in "alcance". Without a location or city it returns the country/global listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textoNoBúsqueda libre en nombre y descripción / Free-text search
ciudadNoCiudad alrededor de la cual buscar, p.ej. "Miami" / City to search around
categoriaNoCategoría: restaurante, tienda, belleza, salud, fitness, hotel… / Category
ubicacionNoUbicación del USUARIO (no la del agente) / The USER's location (not the agent's)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / ciudad / description
      Previous value: -"Filtrar por ciudad, p.ej. \"Miami\" / Filter by city"New value: +"Ciudad alrededor de la cual buscar, p.ej. \"Miami\" / City to search around"
    • addedInput schema / properties / ubicacion / properties / precisionMetros
      Added value: +{
+  "description": "Precisión de la ubicación en metros, si se conoce. Con más de 1000 m no se dan distancias / Location accuracy in meters, if known",
+  "maximum": 100000,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description is the only behavior source. It reveals dynamic radius (5–50 miles), that the radius is reported in 'alcance', and the no-location fallback. It doesn't cover auth or side effects, but the search semantics make those lower-risk; the added behavior still goes well beyond the schema.

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 action and resource, then behavior in a few short sentences. It is duplicated in Spanish and English, which is user-friendly but slightly redundant for an AI agent, keeping it from a 5.

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?

For a moderate-complexity search tool with no output schema, the description plus the complete schema parameter descriptions cover the main invocation decisions. The only gap is that it doesn't explicitly state whether filters like category and location can be combined, and no result schema is described.

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?

Schema coverage is 100%, so a 3 is the baseline. The description adds cross-parameter semantics that the schema lacks: location/city triggers radius search, absence returns country/global listing, and 'alcance' is emitted. It does not restate the per-field descriptions, which is appropriate.

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?

States a specific verb ('Busca'), resource ('directorio público' / public business directory), and scope (Miami–Central America), and enumerates the search dimensions. This differentiates it from sibling search tools like buscar_eventos and buscar_por_servicio by naming the business directory as the target.

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?

Explicitly describes two invocation modes: with location/city it searches a dynamic radius, without them it falls back to a country/global listing. It does not name sibling alternatives or state when not to use it, so it misses the 5-threshold, but gives clear operational context.

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

All Directorio Systema 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