Bidalto

Buscar licitaciones públicas abiertas

search_tenders

Read-onlyIdempotent

Busca licitaciones públicas abiertas en España (Plataforma de Contratación del Sector Público y plataformas autonómicas agregadas; en plazo, actualizado a diario). Filtra por sector o palabra clave, provincia, municipio (busca el nombre en el título y en el órgano de contratación), tipo de contrato, presupuesto base sin IVA y fecha de cierre. Devuelve como máximo 25 resultados, cada uno con su enlace a la ficha en bidalto.com.

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

Input Schema

Name	Required	Description
`tipo`	No	Tipo de contrato.
`orden`	No	Orden: por fecha de cierre (por defecto) o por presupuesto.
`limite`	No	Número de resultados (1-25, por defecto 10).
`sector`	No	Sector o palabra clave: p. ej. "limpieza", "seguridad", "jardinería", "comedores", "mantenimiento", "obras de carreteras", "software".
`municipio`	No	Municipio o texto que debe aparecer en el título o en el órgano de contratación, p. ej. "Getafe".
`provincia`	No	Provincia (nombre o código INE de 2 dígitos), p. ej. "Madrid", "Valencia", "28".
`cierra_antes_de`	No	Solo las que cierran en o antes de esta fecha (AAAA-MM-DD).
`presupuesto_max`	No	Presupuesto base de licitación máximo, en euros sin IVA.
`presupuesto_min`	No	Presupuesto base de licitación mínimo, en euros sin IVA.
`cierra_despues_de`	No	Solo las que cierran en o después de esta fecha (AAAA-MM-DD). Por defecto, hoy.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds genuinely useful behavior: the aggregated data sources, the daily refresh cadence, the hard 25-result cap, and that each result carries a link to its bidalto.com record. It does not discuss pagination or how to reach results beyond the 25 cap.

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?

Three sentences, front-loaded with the purpose and source scope before the filter list and the return shape. Dense but every clause carries information; only the parenthetical about municipio matching is arguably redundant with the schema.

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?

For a 10-parameter search tool with no output schema, the description covers sources, freshness, filtering surface, the hard result cap and the returned link field — enough for an agent to call it correctly and know what comes back. What is missing is routing to the detail/estimation siblings, which is the main completeness gap.

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 one of the 10 parameters is already documented, and the description's list of filters (sector, provincia, municipio, tipo, presupuesto sin IVA, fecha de cierre) largely mirrors it. It does add one real clarification — that municipio matches against both the title and the contracting body — but that nuance is also present in the schema, so the marginal value is modest.

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 and resource ('Busca licitaciones públicas abiertas') and scopes it to Spain's Plataforma de Contratación del Sector Público plus aggregated regional platforms, in-term and updated daily. That is far more specific than a title restatement, though it never names the sibling tools (get_tender / estimate_offer) that this search clearly feeds into.

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 implied by the scope ('abiertas', 'en plazo', daily refresh), which tells the agent this is a discovery entry point rather than a detail lookup. However, there is no explicit statement of when to use this versus get_tender or estimate_offer, and no exclusions or prerequisites are given.

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

All Bidalto tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?