Skip to main content
Glama
Sign In

Subvencióname

by app.subvencioname
OverviewDiscussionsAdmin

buscar_licitaciones

Read-only

Busca contratos públicos de España con el plazo de ofertas abierto (Plataforma de Contratación, TED y BOE). Devuelve objeto, órgano, importe sin IVA y fecha límite. Si «ampliado» no es null, no había nada con ese texto y son contratos parecidos: dilo así.

Input Schema

NameRequiredDescriptionDefault
qNoTexto a buscar en el objeto del contrato («limpieza de edificios», «mantenimiento informático»).
cpvNoDivisión CPV de dos dígitos, p. ej. «45» (obras) o «90» (limpieza).
pageNoPágina de resultados (empieza en 1).
tipoNoTipo de contrato, por su nombre.
ordenNoOrden de los resultados.
organoNoTexto del órgano de contratación.
pageSizeNoResultados por página (25 por defecto, máximo 100).
provinciaNoProvincia por su nombre oficial, p. ej. «La Rioja», «Bizkaia».
importeMaxNoImporte máximo en euros, sin IVA.
importeMinNoImporte mínimo en euros, sin IVA.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tipo / description
      Previous value: -"Tipo de contrato: obras, servicios, suministros…"New value: +"Tipo de contrato, por su nombre."
    • addedInput schema / properties / tipo / enum
      Added value: +[
+  "suministros",
+  "servicios",
+  "obras",
+  "administrativo especial",
+  "privado",
+  "gestión de servicios públicos",
+  "concesión de servicios",
+  "concesión de obras públicas",
+  "concesión de obras",
+  "colaboración público-privada",
+  "patrimonial"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: the data sources, the returned fields, and crucially the semantics of the 'ampliado' fallback (similar-but-not-matching results). It omits pagination/rate-limit behavior, but the fallback disclosure is genuinely useful context.

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?

Three dense sentences with zero filler: purpose and sources first, then return fields, then the critical fallback interpretation. Front-loaded and every sentence earns its place.

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 no output schema, the description usefully names the returned fields (objeto, órgano, importe sin IVA, fecha límite) and explains the 'ampliado' result shape, which is essential for correct agent behavior. Ten parameters are fully covered by the schema, but pagination defaults and ordering semantics beyond the enum are left implicit.

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 (q, cpv, tipo, provincia, importe ranges, etc.) is already documented with examples and constraints. The description adds no parameter-specific syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 verb (buscar) and resource (contratos públicos de España) and narrows the scope to open-deadline tenders from three named sources (Plataforma de Contratación, TED, BOE). This lets an agent distinguish it from siblings like buscar_adjudicaciones (awarded contracts) without opening any schema.

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?

The 'plazo de ofertas abierto' scoping and the explicit instruction on how to interpret a non-null 'ampliado' field give clear usage context and a fallback protocol. It does not explicitly name the sibling tools as alternatives, so it stops short of a full when/when-not routing guide.

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

All Subvencióname toolsInspect
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