Skip to main content
Glama

licitaIA — Spanish public tenders

Buscar licitaciones públicas

buscar_licitaciones
Read-only

Búsqueda pública acotada a publicaciones de los últimos 30 días. Opcionalmente usa soloFuturas para exigir un plazo posterior al momento de consulta, fechaLimiteDesde como límite inclusivo ISO 8601 con zona horaria, y presupuestoMin/presupuestoMax sobre el campo presupuestoBase registrado en euros; los importes desconocidos quedan fuera cuando se pide rango.

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": "buscar_licitaciones"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpvNo
pageNo
limitNo
queryNo
organismoNo
provinciaNo
soloFuturasNoSolo plazos de presentación posteriores al momento de consulta.
presupuestoMaxNoPresupuesto base registrado máximo, en euros.
presupuestoMinNoPresupuesto base registrado mínimo, en euros.
fechaLimiteDesdeNoLímite inferior inclusivo del plazo, con zona horaria explícita.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / fechaLimiteDesde
      Added value: +{
      +  "description": "Límite inferior inclusivo del plazo, con zona horaria explícita.",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d{1,3})?(?:Z|[+-]\\d{2}:\\d{2})$",
      +  "type": "string"
      +}
    • addedInput schema / properties / presupuestoMax
      Added value: +{
      +  "description": "Presupuesto base registrado máximo, en euros.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / presupuestoMin
      Added value: +{
      +  "description": "Presupuesto base registrado mínimo, en euros.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / soloFuturas
      Added value: +{
      +  "description": "Solo plazos de presentación posteriores al momento de consulta.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description goes further by disclosing two non-obvious behaviors: the 30-day lookback window and the fact that records with unknown presupuestoBase are excluded once a budget range is requested. It omits the notable return-size cap (page max 1, limit max 5), which is a real behavioral limitation.

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 whose first clause puts the scope constraint up front, followed by the optional filters; there is no filler or repetition. Density is high enough that a non-Spanish-speaking reader may need a second pass, but nothing is wasted.

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?

With no output schema and 10 parameters (none required), the description leaves important context unstated: what a result looks like, and especially the effective result cap implied by page maximum 1 and limit maximum 5. It covers the filtering semantics well but is incomplete for a tool of this complexity.

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 only 40% across 10 parameters, so the description must compensate and it does for four of them: soloFuturas (deadline after query time), fechaLimiteDesde (inclusive, ISO 8601 with timezone) and presupuestoMin/Max (applied to presupuestoBase, euros, unknown amounts dropped). The remaining six parameters (cpv, page, limit, query, organismo, provincia) are undocumented beyond bare types and patterns.

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 states a specific verb and resource ('Búsqueda pública' over licitaciones/publicaciones) and adds a concrete scope constraint: only publications from the last 30 days. It does not name or contrast itself with the sibling ficha_licitacion, so an agent must infer that this is the list/search tool and that one is the detail lookup.

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 search framing and the 30-day scope acts as an implicit 'use this for recent items' cue, but there is no explicit when-to-use, no when-not-to-use, and no reference to ficha_licitacion as the alternative for a specific tender.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources