Skip to main content
Glama
Consulta Boletines Oficiales - Legislación consolidada

Consulta Boletines Oficiales - Legislación consolidada

boe_ficha_norma

Read-only

Retrieve the full consolidated record for a Spanish legal norm by BOE identifier to verify its current status, derogation, and consolidation before citing it.

Instructions

Ficha completa de una norma consolidada por su identificador BOE (p. ej. BOE-A-1995-25444): título oficial, rango, fechas, si está derogada o anulada, estado de consolidación y ELI. Usa esto para comprobar la vigencia antes de citar.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "boe_ficha_norma"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentificador BOE-A-AAAA-N.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/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=true, so safety is covered. The description adds real behavioral context beyond that: it returns consolidation status and whether the norm is repealed or annulled, making clear this is a point-in-time validity read rather than full text.

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?

Two sentences, zero waste: the resource and identifier are front-loaded, the returned fields are enumerated compactly, and the usage cue closes. Nothing redundant.

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 one required parameter, no output schema and full annotation coverage, the description is nearly self-sufficient — it enumerates the returned fields, which is the key gap left by the absent output schema. Only the response shape/format details 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 coverage is 100% and the single parameter already documents the 'BOE-A-AAAA-N' format; the description only repeats the example identifier. With the schema doing all the work, the baseline of 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?

States a specific verb and resource: 'Ficha completa de una norma consolidada por su identificador BOE', then enumerates exactly what the record contains (título, rango, fechas, derogación/anulación, consolidación, ELI). It is clearly distinguishable from retrieval siblings like boe_texto_articulo, though it never names boe_indice_norma or boe_resolver_norma explicitly.

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?

'Usa esto para comprobar la vigencia antes de citar' gives a concrete trigger tied to a real workflow (checking validity before citing). It lacks any when-not guidance or explicit routing to siblings such as boe_verificar_cita, so it stops short of full alternative coverage.

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