Hoy Planes

Buscar planes

buscar_planes

Read-onlyIdempotent

Busca planes de ocio y cultura en una provincia española por fecha, categoría (temática), ocasión, palabras, precio máximo y distancia a unas coordenadas. Devuelve los más populares primero (o los más cercanos, si se pasan coordenadas), con su ficha en la web.

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": {
      "provincia": "<provincia>"
    },
    "name": "buscar_planes"
  }
}

Input Schema

Name	Required	Description
`lat`	No	Latitud del punto para el filtro de proximidad (con «lng»), en grados decimales: las coordenadas del sitio cerca del cual se quieren los planes (un barrio, una calle, un monumento, un municipio). No es la ubicación del usuario. El servicio no calcula coordenadas: hay que pasarlas.
`lng`	No	Longitud del punto para el filtro de proximidad (con «lat»), en grados decimales. Igual que «lat»: el sitio de referencia de la búsqueda, no la ubicación del usuario.
`desde`	No	Primer día, AAAA-MM-DD (en vez de «fecha»). Rango máximo de 31 días.
`fecha`	No	Una fecha de la agenda: hoy, manana, finde (este fin de semana), semana (esta semana) o proximasemana. Para otras fechas, usa desde y hasta.
`hasta`	No	Último día, AAAA-MM-DD. Si falta, solo el día de «desde».
`texto`	No	Palabras que tiene que tener el plan (título, lugar o descripción): «jazz», «Teatro Lara», «flamenco». No pongas aquí la fecha, la temática ni el sitio, que tienen su campo.
`gratis`	No	Solo planes gratis.
`limite`	No	Cuántos planes devolver (por defecto 10, como mucho 20).
`ocasion`	No	Ocasión: pareja (Planes en pareja), amigos (Planes con amigos), lluvia (Planes para días de lluvia), originales (Planes originales), baratos (Planes baratos), regalar (Planes para regalar).
`radio_km`	No	Con «lat» y «lng», radio en km alrededor del punto (por defecto 5, como mucho 100). Los planes salen del más cercano al más lejano, con su distancia.
`tematica`	No	Temática: teatro (Teatro y espectáculos), musicales (Musicales), monologos (Monólogos), conciertos (Conciertos), exposiciones (Exposiciones), cine (Cine), gastronomia (Gastronomía), ferias-y-fiestas (Ferias, mercadillos y fiestas), visitas-y-excursiones (Visitas guiadas y excursiones), deportes (Deportes), charlas-talleres (Charlas y talleres), ninos (Para niños).
`provincia`	Yes	La provincia: madrid, barcelona, valencia, sevilla, zaragoza, baleares, castellon, alicante, malaga, asturias, murcia, cadiz.
`precio_max`	No	Precio máximo en euros: planes gratis o cuyo precio desde es este o menor. Los de pago sin precio conocido quedan fuera.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare this as a read-only, idempotent, non-destructive, non-open-world operation. The description adds real behavioral context beyond them: relevance ordering (popularity by default), a distance-based ordering switch when coordinates are provided, and the fact that results carry a link to the web ficha. It stops short of covering paging/limits behavior or edge cases such as incomplete coordinate pairs.

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 dense sentences with no filler, front-loaded with the verb and resource before enumerating filters and then the result ordering. Every clause carries information the agent needs.

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 13-parameter search tool with no output schema, the description establishes what it finds, how results are ordered and that each result has a web ficha, which is enough to call it correctly. Remaining gaps are minor: the effect of radio_km without coordinates and the detail-vs-search boundary with ver_plan are left implicit.

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%, so the schema already documents all 13 parameters thoroughly, including defaults and enum meanings; the baseline is 3. The description adds modest value by tying coordinates to the proximity filter and by stating the conditional ordering (popular first, nearest if coordinates are supplied), but it introduces no syntax or format detail the schema lacks.

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 first sentence gives a specific verb (Busca) and resource (planes de ocio y cultura) and names the scope (una provincia española) plus the filter dimensions. It is clearly a search tool, distinct from listar_provincias and ver_plan, though it never names those siblings explicitly.

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?

Usage is only implied: an agent can infer this is the tool for discovering plans and that filtering by date, temática, ocasión, etc. is the intended path. There is no explicit when-to-use vs when-not guidance and no pointer to ver_plan for detail or listar_provincias for choosing a province.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hoy Planes tools Inspect

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.