Skip to main content
Glama
plopez053

ayudas-es-mcp

by plopez053
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Calendario previsto de ayudas

ayudas_previstas
Read-onlyIdempotent

Forecast upcoming Spanish grants from historical BDNS dates so you can prepare documentation before application periods open; statistical estimate, not official.

Instructions

Ayudas que se convocan todos los años y que, según su histórico en la BDNS desde 2021, saldrán en los próximos días, o que este año se están retrasando. Sirve para preparar la documentación antes de que se abra el plazo. Es una PREVISIÓN estadística a partir de las fechas de registro de años anteriores, no un anuncio oficial. Ejemplo: '¿qué ayudas para pymes del País Vasco suelen salir en los próximos 2 meses?' → comunidad 'pais-vasco', beneficiario 'autonomo-o-pyme', dias 60.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diasNoHorizonte en días. Por defecto 60
textoNoPalabras que deben aparecer todas en el título (también en euskera, catalán o gallego). Admite singular/plural; con '*' busca por prefijo (p. ej. 'digital*').
limiteNoPor defecto 15
comunidadNoComunidad autónoma (incluye sus provincias y municipios)
finalidadNoFinalidad o sector de la ayuda
instrumentoNoTipo de ayuda: subvención, préstamo, garantía...
beneficiarioNo'autonomo-o-pyme' = autónomos, pymes y personas con actividad económica; 'entidad-sin-actividad-economica' = asociaciones, fundaciones, entidades públicas; 'particular' = personas físicas sin actividad económica.
administracionNoNivel de la administración convocante
incluir_estatalesNoCon 'comunidad', incluir también las ayudas de ámbito nacional. Por defecto true.
incluir_retrasadasNoIncluir las que ya deberían haber salido este año y no constan. Por defecto true.
incluir_baja_confianzaNoIncluir las de fechas muy irregulares (error típico de ~2 meses). Por defecto false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld/non-destructive, so the safety profile is settled. The description adds genuinely useful domain context the annotations cannot: it is a statistical forecast with inherent error, not an official announcement, which sets correct expectations for the agent and the user. Confidence/error behavior is also surfaced in the incluir_baja_confianza param.

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?

Front-loads the purpose, then the use case, then the critical caveat, then a concrete example. No filler; every sentence adds selection or interpretation value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter, all-optional, no-output-schema tool, the description supplies scope, intent, caveat and example, while annotations carry the safety profile and the schema carries parameter detail. Nothing needed to select or invoke it correctly is missing.

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 all 11 parameters are already documented with defaults, enums and semantics. The example supplies a light mapping from intent to parameters (dias 60, beneficiario, comunidad), but adds little beyond what the schema already states. 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?

States a specific resource (ayudas/grants) and a distinctive scope: grants that recur annually and, per BDNS history since 2021, are due soon or are delayed. Cleverly distinguishes itself from a plain search tool by framing the output as a forecast calendar rather than a listing.

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?

Gives a clear use case ('preparar la documentación antes de que se abra el plazo') and a worked example mapping a natural-language query to specific parameters (comunidad, beneficiario, dias). It does not explicitly name a sibling like ayudas_buscar as the alternative for already-open grants, relying on the 'previsión, no anuncio oficial' framing instead.

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

Deploy Server

Other Tools