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

Consulta Boletines Oficiales - Legislación consolidada

ue_texto_articulo

Read-only

Retrieves the literal text of an article in an EU regulation, directive, or decision in the consolidated version in force, in Spanish or English, and returns IDIOMA_NO_DISPONIBLE if unavailable.

Instructions

Texto literal de un artículo de un reglamento, directiva o decisión de la UE en la versión consolidada que rige hoy (o en el texto original si no hay consolidada), en castellano o en inglés. Si el texto no existe en el idioma pedido devuelve IDIOMA_NO_DISPONIBLE: nunca lo sustituye por otro idioma. El texto consolidado es documental, sin efecto jurídico: en cualquier cita da también "url_doue" (lo auténtico es el DOUE) y "version_desde".

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": {
      "norma": "<norma>",
      "articulo": "<articulo>"
    },
    "name": "ue_texto_articulo"
  }
}

Input Schema

NameRequiredDescriptionDefault
normaYesCita, siglas o CELEX del acto ("RGPD", "Reglamento (UE) 2024/1689", "32012R1215").
idiomaNoCastellano ("es", por defecto) o inglés ("en").
articuloYesNúmero del artículo, p. ej. "17" o "4 bis".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the read-only/open-world annotations, the description discloses two behaviours an agent could not otherwise know: a missing language returns the sentinel IDIOMA_NO_DISPONIBLE and is never silently substituted, and the consolidated text is documentary with no legal effect, so any citation must also carry 'url_doue' and 'version_desde'. That is exactly the kind of failure-mode and citation-obligation context annotations cannot convey.

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 core capability is front-loaded in the first clause, followed by the language-fallback rule and then the citation obligation; there is no filler. It is dense — three distinct rules packed into a single sentence block — but every sentence earns its place.

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?

For a three-parameter read tool with no output schema, the description covers the source version, language behaviour and error signal, and the mandatory companion fields for citing the result. An agent can call it correctly and handle the failure case without consulting anything else.

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% and already documents the norma citation/CELEX forms, the es/en enum and the default, and the article number format. The description adds only the language-fallback semantics, so the baseline of 3 applies — it does not extend meaning much past the schema.

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+resource: returns the literal text of a single article of an EU regulation, directive or decision, in the consolidated version in force or the original if none exists. The EU scope plus the 'artículo' granularity clearly separates it from sibling tools like ue_buscar_normas (search) and boe_texto_articulo (national law).

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?

The fallback rule (consolidated in force, otherwise original text) implicitly tells the agent which version it will get, which is useful context. However, it never says when to prefer this over ue_ficha_norma or ue_verificar_cita, or that the agent should first resolve the act with ue_buscar_normas, leaving the routing mostly to inference.

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