Skip to main content
Glama

buscar_adjudicaciones

Read-only

Contratos públicos ya adjudicados, por NIF de la empresa adjudicataria, por texto o por provincia. Sirve para ver qué gana una empresa y cuándo vence cada contrato. Solo empresas: no hay datos de personas físicas.

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

Input Schema

NameRequiredDescriptionDefault
qNoTexto a buscar en el objeto del contrato.
nifNoNIF de la empresa adjudicataria (p. ej. B12345678). Con NIF se ignora el texto.
pageNoPágina de resultados (empieza en 1, máximo 500).
pageSizeNoResultados por página (25 por defecto, máximo 100).
provinciaNoProvincia por su nombre oficial, p. ej. «La Rioja», «Bizkaia».
vence_antesNoSolo contratos que vencen antes de esta fecha (AAAA-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / page / description
      Previous value: -"Página de resultados (empieza en 1)."New value: +"Página de resultados (empieza en 1, máximo 500)."
    • addedInput schema / properties / page / maximum
      Added value: +500
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and closed-world scope are covered structurally. The description adds real behavioral context beyond that: results are limited to companies with no natural-person data, and results reveal award and expiry dates. It does not address result ordering, empty-result behavior, or pagination limits.

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 short sentences, front-loaded with the resource and filters before the purpose statement. Effectively no filler, though the 'Solo empresas' caveat could be placed more prominently given it prevents wasted calls.

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?

This is a six-parameter, fully optional, read-only search tool with a fully annotated schema and no output schema, so the description need not explain return values. The main gaps are result ordering and how empty results behave, which are minor for a filter-based search tool whose parameters are already well described.

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 coverage is 100%, so the schema itself documents q, nif, page, pageSize, provincia and vence_antes, including the key precedence rule that NIF overrides text. The description only gestures at these filters ('por NIF... por texto o por provincia') without adding format or precedence detail, so baseline 3 applies.

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 names a specific resource ('Contratos públicos ya adjudicados') and the three filter axes (NIF, texto, provincia), and adds the analytical purpose ('ver qué gana una empresa y cuándo vence cada contrato'). It implicitly separates itself from sibling resources like convocatorias/licitaciones through 'ya adjudicados', but never names an alternative tool outright, so it falls just short of a 5.

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?

Use is implied by 'Sirve para ver qué gana una empresa y cuándo vence cada contrato', which tells the agent the intended analytical question. However, no sibling tools are named and no explicit when-not guidance is given. The 'Solo empresas' line is a valuable scope exclusion but concerns data coverage rather than tool selection.

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