Skip to main content
Glama

Directorio Systema

by app.scalesystema
OverviewDiscussionsAdmin

Ver promociones / View promotions

ver_promociones

ES: Promociones vigentes de los negocios del directorio, por ubicación {lat,lng} o ciudad (radio dinámico de 5 a 50 millas alrededor de ese punto). Sin ubicación ni ciudad devuelve el alcance país/global. / EN: Active promotions from directory businesses, by location {lat,lng} or city (dynamic 5 to 50 mile radius around that point). Without a location or city it returns the country/global scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ciudadNoCiudad alrededor de la cual buscar / City to search around
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 / Filter by city"New value: +"Ciudad alrededor de la cual buscar / 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

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose a meaningful behavioral trait (dynamic 5-to-50-mile radius) and the fallback to global when no location is given, which goes beyond the schema. However, it does not explicitly state that this is a read-only/query operation, mention result format or pagination, or address edge cases like both parameters being provided.

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 compact and front-loaded: the first sentence identifies the purpose and scoping. The inclusion of a full English translation of the Spanish text adds some redundancy for an AI agent that could parse either language, but overall it is concise and earns its place for a bilingual context.

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?

For a tool with zero required parameters and a nested geometry object, the description adequately explains the two main paths (localized radius vs global fallback) and the dynamic radius range. It is less complete because it does not address what happens when both 'ciudad' and 'ubicacion' are supplied, nor what the returned promotion objects look like, especially given no output schema is provided.

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?

With 100% schema description coverage, the baseline is 3, but the description adds value beyond the schema by explaining the relationship between location/city and the dynamic radius, and the behavior when neither parameter is supplied. This gives the agent a functional understanding of how the parameters relate to the search scope.

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?

The description clearly states the tool is for viewing promotions ('Ver promociones') and specifies what it returns: 'Active promotions from directory businesses' with optional location scoping. This is a specific verb+resource and is distinct from siblings like buscar_negocios or buscar_eventos, though it doesn't explicitly name the sibling alternatives.

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?

The description gives clear context on how to use the tool: provide a location or city for a localized radius, or omit both for the country/global scope. However, it does not provide guidance on when to choose this tool over alternative directory tools, leaving the selection to inference from the name and resource.

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