Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

search_spain_public_tenders

Read-onlyIdempotent

Search Spain's official PLACSP public tender feeds for open or awarded contracts, filtered by region, keywords, CPV code, EUR budget, or SME minor contracts.

Instructions

Parse Spain's official Plataforma de Contratación del Sector Público (PLACSP CODICE Atom feeds) into clean JSON: open public tenders (licitaciones), minor contracts (contratos menores), CPV codes, EUR budgets, and winning NIF contract awards (corridordata/spain-public-tenders-contratacion).

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_public_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOptional city, province, or Autonomous Community substring (e.g. 'Madrid', 'Barcelona').
feedTypeNoGeneral contracting profiles (`licitaciones`) or SME minor contracts (`contratos_menores`).licitaciones
keywordsNoSpanish or English keywords matched against contract title or authority.
maxItemsNoMaximum Spanish public tender or award notices to return.
cpvPrefixesNoCPV code prefixes (e.g. ['72'] for IT/Software, ['79'] for Consulting, ['45'] for Construction).
minBudgetEurNoMinimum tax-exclusive budget in EUR.
statusFilterNoFilter for open tenders (`open_only`), awarded contracts (`awarded_only`), or all.open_only
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so safety and idempotency are covered by structured data. The description adds genuine context by naming the upstream source (official PLACSP CODICE Atom feeds) and the shape of the output, but says nothing about data freshness, pagination, or latency.

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 dense sentence front-loads the data source and the output contract, which is efficient. It loses a little by re-enumerating fields that the schema already describes (CPV codes, budgets, awards).

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?

With 8 all-optional parameters and no output schema, the description usefully compensates by describing what the returned JSON contains: tenders, minor contracts, CPV codes, budgets and awards. It is broadly complete for a filtered search tool backed by rich annotations.

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 every parameter including region, feedType, statusFilter and maxTotalChargeUsd is already documented in the schema. The description names some of the same fields (CPV codes, EUR budgets) but adds no syntax, format, or interaction detail beyond the schema baseline.

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?

States a specific verb+resource: parses Spain's PLACSP CODICE Atom feeds into clean JSON covering tenders, minor contracts, CPV codes, budgets and awards. The geographic and source specificity distinguishes it from generic siblings like search_global_tenders, though it never explicitly names those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no routing to search_global_tenders, search_uk_france_tenders, or search_spain_boe_grants. Usage is only implied by the geographic framing and the feedType/statusFilter enums in the schema.

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