Skip to main content
Glama

CarteleraCines.es

by es.carteleracines

find_nearby_cines

Read-onlyIdempotent

Busca cines cercanos a un punto, para "qué cines tengo cerca" o "cines cerca de mí"/"cerca de tal sitio". Si el cliente puede compartir coordenadas reales del usuario, pásalas en lat/lng; si no, pasa una localidad (p.ej. "Córdoba") y se usa el centro de esa localidad como referencia. Devuelve los cines ordenados por distancia en km dentro del radio indicado.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitud. Si se usa, lng también es obligatoria.
lngNoLongitud. Si se usa, lat también es obligatoria.
limitNoOpcional. Por defecto 10, máximo 50.
radio_kmNoOpcional. Por defecto 25 km, máximo 200 km.
localidadNoCiudad usada como origen cuando no se dispone de lat+lng. Debe indicarse localidad O la pareja lat+lng.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that results are ordered by distance in km, and explains behavior with coordinates vs. locality. No contradictions.

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 concise sentences that front-load the purpose. Every sentence is informative with no wasted words.

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?

Despite lacking an output schema, the description mentions the return (cines ordenados por distancia). It covers input constraints well, though it doesn't mention error handling or no-results case.

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 description coverage is 100%. The description adds clarifying mutual exclusivity of lat+lng and localidad, defaults for limit and radio_km, and natural language context for parameter usage.

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?

The description clearly states a specific verb+resource: 'Busca cines cercanos a un punto', and provides natural language queries like 'qué cines tengo cerca'. It distinguishes from siblings like get_cartelera_cine and get_cartelera_localidad by focusing on geo-proximity.

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 explicit instructions on when to use lat/lng versus localidad, and mentions default radius. It lacks explicit exclusions for alternatives, but the context implies the use case (finding nearby cinemas vs. getting cartelera for a specific locality).

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

All CarteleraCines.es toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: find_movie for fuzzy title search, find_movie_showtimes for specific movie showtimes, find_nearby_cines for nearby cinemas, etc. Overlaps are minimal and descriptions clarify boundaries.

Naming Consistency5/5

All tool names follow a consistent 'verb_noun' pattern with underscores and lowercase (e.g., find_movie, get_cartelera_cine, where_to_watch_online). No mixed conventions.

Tool Count5/5

11 tools cover the domain of a cinema information server without being overwhelming or insufficient. Each tool addresses a specific user need (search, showtimes, recommendations, streaming).

Completeness4/5

The tool set covers major user intents: finding movies, showtimes, cinemas, details, recommendations, and streaming availability. Minor gap: no tool for cinema amenities or user reviews, but core workflows are covered.

Resources