Skip to main content
Glama

Gracieta: teatro, humor y musicales en España

Ver espectáculo

ver_espectaculo
Read-onlyIdempotent

Devuelve la ficha de un espectáculo por su slug: descripción, recinto, rango de precios, próximas funciones y en qué plataformas se vende, a qué precio y con qué enlace de compra (plataformas[].url; comprar es el más barato). Úsala tras buscar_espectaculos para comparar dónde sale más barato o cuando pregunten por horarios, precio o dónde comprar entradas de un espectáculo concreto.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "ver_espectaculo"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSlug del espectáculo, tal como lo devuelve buscar_espectaculos. Ejemplo: "el-rey-leon".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral value beyond that by disclosing the returned structure, including the nested `plataformas[].url` field and the rule that `comprar` marks the cheapest option — information no annotation or schema conveys (there is no output schema). It stops short of describing error behavior for an unknown slug.

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 verb and resource, then the return payload, then a usage sentence — a logical order with no filler. The first sentence is long and clause-dense, but each clause names a distinct part of the returned record, so little could be cut without losing information.

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?

With no output schema, the description carries the burden of explaining return values and does so well, listing the record's fields and the platform/purchase-link structure. For a single-parameter read tool that is nearly complete; only the failure mode for an invalid or unknown slug is unaddressed.

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 100%: the slug parameter already documents the pattern, the source of the value, and an example ("el-rey-leon"). The description only restates "por su slug", so the baseline of 3 applies — the schema does all the heavy lifting here.

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?

Opens with a specific verb and resource ("Devuelve la ficha de un espectáculo") plus the lookup key (slug), then enumerates exactly what the record contains: description, venue, price range, upcoming performances and sales platforms with prices and purchase links. This clearly separates it from the sibling buscar_espectaculos, which finds shows rather than returning one full record.

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

Usage Guidelines5/5

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

Explicitly states the trigger conditions: use it after buscar_espectaculos, to compare where a show is cheapest, or when asked about schedules, prices, or where to buy tickets for a specific show. The alternative (search) is named along with the ordering relationship between the two calls.

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