A
license-
qualityB
maintenanceDiscover tech events, startup meetups, AI events across cities including hidden ones.
37
2
MIT
What a Plan! — MCP Server
Server Details
Descubre eventos en España: filtra por texto, categoría, ubicación, precio y fecha. 38 categorías.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.2/5.0
Tool DescriptionsA
Average 4/5 across 3 of 3 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool has a clear, distinct purpose: searching for events, getting details on a specific event, and listing categories. No overlap or ambiguity.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (search_events, get_event, list_categories), making them predictable and easy to remember.
Tool Count5/5
Three tools is an appropriate and focused set for a read-only event discovery server. Each tool earns its place, covering the essential workflow of search, detail, and category listing without bloat.
Completeness5/5
For a read-only event browsing domain, the set covers the full typical agent workflow: search with filters, get details, and list categories for context. No obvious gaps.
Available Tools
3 toolsget_eventAInspect
Obtiene los detalles completos de un evento específico por su slug. Usa esta herramienta después de search_events para obtener información detallada.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Slug único del evento (ej: "concierto-rock-leon-2026"). Obligatorio. |
Tool Definition Quality
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states the tool retrieves 'complete details', but does not disclose any potential side effects, authentication needs, or return format. For a read-only tool, this is adequate but could be improved with specifics on response contents.
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?
The description is two sentences with no wasted words. It front-loads the purpose and follows with usage instruction. Perfectly concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers purpose and usage but lacks details on output/return value. Since there is no output schema, the agent would benefit from knowing what fields or information are included in 'complete details'. This gap reduces completeness.
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% and the schema already describes the 'slug' parameter well. The description adds an example but no additional semantic context beyond what the schema provides, so 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?
The description clearly states the tool's purpose: retrieving complete event details by slug. It distinguishes from sibling tools by referencing search_events and stating that this tool provides detailed information after a search.
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 explicitly instructs to use this tool after search_events, providing clear workflow context. While it doesn't explicitly list when not to use it, the guidance is sufficient for an agent to understand the intended usage sequence.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_categoriesAInspect
Lista todas las categorías de planes disponibles en What a Plan! (ej: Música en Directo, Teatro, Gastronomía, Deportes, etc.)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Definition Quality
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the transparency burden. It implies a read-only operation by stating it lists categories, which is sufficient for a simple retrieval tool. No behavioral traits like side effects or authentication are needed for this straightforward function.
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?
The description is a single sentence with no fluff, efficiently conveying the tool's purpose and providing examples. Every word earns its place.
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?
Given the tool has no parameters, no output schema, and is a simple list operation, the description is complete enough. It includes examples of categories, which helps the agent understand the output. It could mention if the list is static or dynamic, but not necessary.
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?
There are no parameters (0 params), and schema coverage is 100%. According to guidelines, baseline is 4. The description adds no parameter details, but none are needed.
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 verb 'list' clearly indicates the operation, and the resource 'categories' is explicit. The description provides examples of categories, distinguishing it from sibling tools get_event and search_events.
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?
The description states what the tool does but does not specify when to use it compared to siblings or provide any exclusions. The context signals and sibling names help infer usage, but the description itself lacks explicit guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_eventsAInspect
Busca planes y eventos en What a Plan! usando múltiples filtros. Usa esta herramienta cuando alguien pregunte por planes, eventos, actividades, o qué hacer. Para filtrar por ubicación, proporciona coordenadas lat/lng y radio en metros (puedes determinar coordenadas desde nombres de ciudades). Ejemplos de consultas: "planes en León para niños", "conciertos gratis este fin de semana", "qué hacer mañana en Valladolid"
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | Latitud del centro de búsqueda (ej: 42.5987 para León). Proporciónala SEMPRE que sepas la ubicación. | |
| lng | No | Longitud del centro de búsqueda (ej: -5.5669 para León). Proporciónala junto con lat. | |
| city | No | Nombre de ciudad como fallback si no puedes determinar coordenadas (menos preciso que lat/lng) | |
| limit | No | Número máximo de resultados (default: 20, máx: 50) | |
| radius | No | Radio de búsqueda en metros (default: 10000 = 10km). Usa 20000 para área metropolitana. | |
| search | No | Palabras clave en título o descripción (ej: "niños", "rock", "gratis", "gastronomía") | |
| category | No | Nombre o slug de categoría (ej: "Música en Directo", "musica-en-directo") | |
| end_date | No | Fecha máxima en formato YYYY-MM-DD (ej: "2026-06-07" para fin de semana) | |
| max_price | No | Precio máximo (ej: 20) | |
| min_price | No | Precio mínimo (ej: 0 para gratis) | |
| start_date | No | Fecha mínima en formato YYYY-MM-DD (ej: "2026-06-05") |
Tool Definition Quality
A3.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as whether the tool is read-only, auth requirements, rate limits, or side effects. The description only focuses on usage, not behavior.
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?
The description is 4 sentences and front-loads the purpose. It is reasonably concise, though the second and third sentences could be merged. No redundant or wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 11 parameters all described in schema and no output schema, the description covers usage context and examples. However, it lacks information about output format or pagination. For a search tool, this is adequate but not complete.
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%, so baseline is 3. The description adds value by explaining usage patterns (e.g., 'puedes determinar coordenadas desde nombres de ciudades') and giving example keywords. This goes beyond the schema's per-parameter descriptions.
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 it searches for plans/events using multiple filters. It distinguishes from siblings 'get_event' (single event) and 'list_categories' (categories) by specifying it's a multi-filter search 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?
It explicitly states when to use the tool: 'when someone asks about plans, events, activities, or what to do.' It provides examples and explains the preference for lat/lng over city. However, it does not include when not to use it or alternatives beyond sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityBmaintenanceProvides music events, concerts, music festivals, nightclubs and other events information.172MIT
- AlicenseAqualityBmaintenanceDiscover and book theatre, shows, events, tours and experiences across 700+ cities worldwide on tickadoo® with real-time pricing and booking links.4141MIT
- Flicense-qualityCmaintenanceEnables searching and retrieving details of over 500,000 Spanish government grants and subsidies from the official BDNS database, without requiring an API key.
