Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

search_spain_boe_grants

Read-onlyIdempotent

Search official Spanish bulletins for recent government grants, subsidies, tenders, and BORME corporate registry acts by keyword, province, or ministry, with configurable date range and result limits.

Instructions

Extract official Spanish government grants and subsidies (BOE Subvenciones / Ayudas), official announcements, and provincial corporate registry acts (BORME Registro Mercantil) via BOE Datos Abiertos (corridordata/spain-boe-borme-grants-signals).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_spain_boe_grants"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourcesNoOfficial Spanish bulletins to scan.
daysBackNoRecent business days to scan.
keywordsNoSpanish keywords, ministries, or provinces (e.g. ['subvenciones', 'digitalización', 'Madrid']).
maxItemsNoMaximum BOE/BORME items to return.
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds provenance (BOE Datos Abiertos dataset) but says nothing about cost behavior despite a maxTotalChargeUsd pay-per-event parameter, nor about result volume, latency, or whether scanning is capped by bulletin limits.

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?

A single sentence that front-loads the resource and folds the data source into a trailing clause, with no repetition. The heavy backticked identifiers (Spanish and English aliases, actor slug) add mild visual noise but no wasted sentences.

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 a read-only, all-optional search tool with 100% schema coverage and no output schema, the description supplies the domain, the bulletins covered, and the dataset of origin — enough for an agent to call it correctly. Return shape is the only omission, and the sibling ecosystem plus parameter names make the result type predictable.

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%, with every parameter documented including enums, defaults, and min/max bounds, so the schema carries the parameter burden. The description adds no semantics beyond it — notably it does not clarify how the 'sources' enum value boe_tenders relates to the 'official announcements' phrasing.

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 uses a specific verb ('Extract') with named resources: Spanish government grants/subsidies, official announcements, and BORME corporate registry acts, plus the underlying dataset. It is clear what the tool retrieves, though it never distinguishes itself explicitly from similarly-named siblings such as search_spain_public_tenders or search_eu_horizon_grants.

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 by the content domain (Spanish BOE/BORME publications); there is no statement of when to pick this over the tender or EU-grant siblings, and no exclusions or prerequisites. An agent must infer the selection criteria from the noun phrases alone.

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