Skip to main content
Glama

Gracieta: teatro, humor y musicales en España

Calendario de una ciudad

calendario_ciudad
Read-onlyIdempotent

Agenda de una ciudad día a día para los próximos días (hasta 14): qué espectáculos hay cada jornada. Úsala para «qué hacer esta semana en Sevilla», «qué hay hoy en Madrid» o «planes para el sábado en Bilbao».

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": {
      "ciudad": "<ciudad>"
    },
    "name": "calendario_ciudad"
  }
}

Input Schema

NameRequiredDescriptionDefault
diasNoCuántos días mostrar (1-14, por defecto 7).
desdeNoPrimer día, YYYY-MM-DD. Por defecto hoy en España.
ciudadYesSlug de la ciudad. Ejemplo: "madrid".
limiteNoMáximo de espectáculos (1-30, por defecto 20).
categoriaNoSlug de categoría para filtrar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/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 fully covered elsewhere. The description adds the useful behavioral framing that results are organized per day within a rolling window of at most 14 days. It does not say how days with no events appear or whether the window is anchored to today.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler: the first defines the output shape and the hard limit, the second gives usage triggers. The most decision-relevant information (day-by-day agenda, 14-day cap) is front-loaded.

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 read-only, five-parameter tool with full schema coverage and no output schema, the description supplies purpose, scope and usage triggers, which is close to sufficient. Minor gaps remain around result grouping and empty-day behavior, but nothing that would cause a wrong invocation.

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 (dias, desde, ciudad, limite, categoria) is already documented with defaults and formats. The description only restates the 14-day window, adding no meaning about filtering, the category slug, or how desde interacts with dias.

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 states a concrete resource and shape: a city's day-by-day agenda of shows for the coming days, capped at 14. That is specific enough to distinguish it from a plain event search, though it never names a sibling tool to sharpen the contrast.

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?

Three example queries («qué hacer esta semana en Sevilla», «qué hay hoy en Madrid», «planes para el sábado en Bilbao») show exactly the intent that should trigger this tool, covering multi-day, same-day and weekend cases. It stops short of saying when NOT to use it, e.g. instead of buscar_espectaculos for a targeted query.

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