Skip to main content
Glama

Detalle de una subvención o licitación

detalle_oportunidad
Read-only

Devuelve el detalle completo de UNA subvención (BDNS) o licitación (PLACSP) por el enlace de su ficha (el que dan buscar_oportunidades o listar_entradas): organismo, importe, plazo, lugar, tipo y procedimiento, CPV, lotes, concesiones y beneficiarios, o adjudicatarios si ya está adjudicada. Sin enlace, codigo_bdns de una subvención, o nif_organo y expediente de una licitación. Úsala para resumir o comparar sin salir de Boletín Claro. Disponible en todos los planes, también en Gratis. Usa solo los datos que devuelve: no completes importes, plazos, fechas ni estados, no digas que algo sigue abierto si su estado no lo dice y cita el enlace a la ficha de cada resultado. Coste: 5 créditos.

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

Input Schema

NameRequiredDescriptionDefault
enlaceNoEl enlace /subvencion/… o /licitacion/… que dan buscar_oportunidades o listar_entradas (no el id de la entrada)
expedienteNoLicitación sin enlace: código de expediente, p. ej. 3/2026
nif_organoNoLicitación sin enlace: NIF del órgano, con expediente
codigo_bdnsNoSubvención sin enlace: su código BDNS

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / enlace / description
      Previous value: -"El enlace /subvencion/… o /licitacion/… que dan buscar_oportunidades, mis_novedades o listar_entradas (no el id de la entrada)"New value: +"El enlace /subvencion/… o /licitacion/… que dan buscar_oportunidades o listar_entradas (no el id de la entrada)"
  2. Added

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 the description is consistent with that, but it adds real behavior beyond them: cost of 5 credits, availability on all plans including Gratis, and data-fidelity rules (do not invent importes, plazos, fechas or estados, do not claim something is open unless its status says so, and cite the link per result). It does not cover failure or not-found behavior, which keeps it short of a 5.

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?

The purpose is front-loaded in the first clause, followed by input fallbacks, scope, and behavioral rules in a compact sequence. It is dense but appropriately sized for a tool with four optional parameters and no output schema; the field enumeration is slightly long but earns its place by describing the return.

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?

With no output schema, the description carries the full burden of describing the return, and it does so by listing organismo, importe, plazo, lugar, tipo y procedimiento, CPV, lotes, concesiones, beneficiarios and adjudicatarios. Combined with the cost, plan availability, and data-fidelity rules, an agent has everything needed to call it correctly.

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 the schema already documents all four parameters, including the expected /subvencion/… or /licitacion/… link format and the fallback fields. The description restates those mappings (codigo_bdns for subvenciones, nif_organo + expediente for licitaciones) without adding format or validation detail beyond the schema, so the baseline of 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 precise verb and resource: returns the complete detail of ONE subvención (BDNS) or licitación (PLACSP) given the link to its record. It names the sibling tools that produce that link (buscar_oportunidades, listar_entradas), so the agent can tell it apart from search tools and from ver_entrada 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?

Gives clear context: use it to summarize or compare without leaving Boletín Claro, and specifies the input alternatives (enlace, or codigo_bdns for a subvención, or nif_organo + expediente for a licitación). There is no explicit when-not guidance against similar siblings such as ver_entrada or expediente, which is the only gap.

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.