Skip to main content
Glama

Gracieta: teatro, humor y musicales en España

Buscar espectáculos

buscar_espectaculos
Read-onlyIdempotent

Busca espectáculos vigentes en España (teatro, musicales, monólogos, magia, circo, danza...) por ciudad, categoría, fechas o texto, y devuelve el precio desde, la página de Gracieta donde se comparan las entradas y en comprar el enlace directo para comprar en la plataforma más barata. Úsala para preguntas como «qué hay en Madrid este fin de semana», «monólogos en Valencia», «entradas para El Rey León», «planes con niños en Sevilla» o «comedy shows in Barcelona», y siempre que pidan qué ver o qué hacer en una ciudad española.

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

Input Schema

NameRequiredDescriptionDefault
desdeNoPrimer día, YYYY-MM-DD, hora de España. Ejemplo: "2026-12-18".
hastaNoÚltimo día, YYYY-MM-DD. Máximo 45 días desde "desde". Si falta, un solo día.
textoNoTexto del título; da igual mayúsculas y tildes. Ejemplo: "rey leon".
ciudadNoSlug de la ciudad, por ejemplo "madrid" (ver listar_ciudades).
limiteNoResultados por página (1-20, por defecto 10).
paginaNoPágina, desde 1.
categoriaNoSlug de la categoría, por ejemplo "musicales" (ver listar_categorias).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description's job is supplementary. It does add genuinely new behavioral context by explaining the return shape (precio desde, Gracieta comparison page, direct purchase link in `comprar`), which the annotations do not convey. It omits operational constraints like the 45-day window or pagination behavior, but those live in 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?

Front-loaded with the core purpose and return value before the usage examples, and no sentence is purely filler. The second sentence is a long chain of five example queries, which is mildly repetitive given the first sentence already enumerates the verticals, but it does real disambiguation work for an agent matching user phrasings.

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 7-parameter, all-optional search tool with no output schema, the definition covers purpose, routing and return contents, which is what an agent needs to select and call it. Missing only is a pointer to the sibling detail tool (ver_espectaculo) and to listar_ciudades/listar_categorias for the slug parameters, which the schema mentions but the description does not reinforce.

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 description coverage is 100%, so every parameter (desde, hasta, texto, ciudad, limite, pagina, categoria) is already documented with format, pattern and examples. The description only restates the filter axes at a high level ('por ciudad, categoría, fechas o texto') without adding format, defaults or edge-case semantics. Baseline 3 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 concrete verb and resource ('Busca espectáculos vigentes en España') and enumerates the searchable dimensions (ciudad, categoría, fechas, texto) plus the verticals covered (teatro, musicales, monólogos, magia, circo, danza). It compounds this with a clear description of what comes back ('precio desde', the Gracieta comparison page, and the `comprar` purchase link), so an agent knows exactly what this tool yields versus a catalogue-listing tool.

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?

Gives strong positive routing with concrete example utterances ('qué hay en Madrid este fin de semana', 'monólogos en Valencia', 'comedy shows in Barcelona') and a catch-all rule ('siempre que pidan qué ver o qué hacer en una ciudad española'). It never states when NOT to use it or points to a specific alternative such as ver_espectaculo for a single show's details, so it stops short of full when/when-not guidance.

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