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

Consulta Boletines Oficiales - Legislación consolidada

boe_texto_articulo

Read-only

Retrieves the literal current text of a consolidated legal article or block by BOE identifier and article title or number, enabling accurate legal citation.

Instructions

Texto literal de un artículo o bloque de una norma consolidada, en la versión vigente hoy. Acepta el identificador del bloque (p. ej. "a22") o el título del artículo (p. ej. "Artículo 22" o "22"). Es la única forma admisible de citar el contenido de un precepto.

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>",
      "articulo": "<articulo>"
    },
    "name": "boe_texto_articulo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentificador BOE-A-AAAA-N.
articuloYesBloque o artículo, p. ej. "a22", "Artículo 22" o "22".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context that the returned text is the currently-in-force consolidated version, but says nothing about failure behavior when an article id is not found or about response size.

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 short sentences, front-loaded with what is returned, then accepted input forms, then the citation rule. No filler.

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 correctly states that the return value is the literal text of the block, and it explains accepted identifier forms. Minor gap: no mention of what happens on an invalid or ambiguous article reference.

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 schema already documents both parameters with the same example formats ('a22', 'Artículo 22', '22') that the description repeats. The description adds no syntax or format detail beyond the schema, so 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+resource: returns the literal text of an article or block of a consolidated norm, in the version in force today. This clearly separates it from siblings like boe_indice_norma or boe_ficha_norma, which describe rather than quote content.

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 closing sentence ('Es la única forma admisible de citar el contenido de un precepto') gives a clear usage mandate for citation. It does not, however, explicitly name the alternative tools (e.g. boe_indice_norma for locating blocks, boe_verificar_cita for validating) or state when not to use it.

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