Skip to main content
Glama
Sign In

Directorio Systema

by app.scalesystema
OverviewDiscussionsAdmin

Buscar eventos / Search events

buscar_eventos

ES: Cartelera de eventos públicos próximos (conciertos, ferias, shows) de los negocios del directorio, filtrable por texto, ubicación {lat,lng} o ciudad (radio dinámico de 5 a 50 millas alrededor de ese punto) y días. Los boletos se compran en la página web del evento (urlBoletos). / EN: Upcoming public events (concerts, fairs, shows) from directory businesses, filterable by text, location {lat,lng} or city (dynamic 5 to 50 mile radius around that point) and days ahead. Tickets are purchased on the event's web page (urlBoletos).

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_eventos"
  }
}

Input Schema

NameRequiredDescriptionDefault
diasNoSolo eventos dentro de N días (sin esto: todos los futuros) / Only events within N days
textoNoFiltro libre: nombre del evento, lugar o negocio / Free-text filter
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
      Added value: +{
+  "additionalProperties": false,
+  "description": "Ubicación del USUARIO (no la del agente) / The USER's location (not the agent's)",
+  "properties": {
+    "lat": {
+      "maximum": 90,
+      "minimum": -90,
+      "type": "number"
+    },
+    "lng": {
+      "maximum": 180,
+      "minimum": -180,
+      "type": "number"
+    },
+    "precisionMetros": {
+      "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"
+    }
+  },
+  "required": [
+    "lat",
+    "lng"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It adds useful behavioral details: dynamic 5-to-50-mile radius, public events only, and that tickets are purchased externally via urlBoletos. It does not describe response shape, pagination, or ordering, but for a read-only search tool the key behavior is well covered.

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 purpose and filter capabilities, and the ticket note is relevant. The bilingual duplication is expected for a Spanish/English tool and is not wasted. It is slightly longer than strictly necessary but remains focused and efficient.

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 tool with four parameters, a nested object, and no output schema, the description provides substantial context: scope, filters, radius behavior, and external ticket purchase. It lacks explicit detail about the result list's fields and ordering, but it is complete enough for an agent to invoke the tool correctly.

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 the baseline is 3, but the description adds genuine meaning beyond the schema by explaining the dynamic radius around a city or location. It also clarifies the event type and external-ticket behavior, which helps the agent understand how the location and city parameters affect results.

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 identifies the tool as providing upcoming public events from directory businesses and lists the main filter dimensions (text, location, city, days). It is clear enough to distinguish from business-search siblings, but it never explicitly states when to use this over a named alternative.

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?

The description gives clear context: this is for upcoming public events like concerts, fairs, and shows, with filters. It does not explicitly mention exclusions or alternatives, but the context is sufficient for an agent to know it is the events search tool rather than one for businesses, promotions, or reservations.

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