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

Consulta Boletines Oficiales - Legislación consolidada

ue_ficha_norma

Read-only

Retrieves official EU act fact sheets from citations, acronyms, or CELEX numbers, including title, date, in-force status, consolidated versions, modifying acts, and EUR-Lex/DOUE links.

Instructions

Ficha de un reglamento, directiva o decisión de la UE: título oficial (en castellano o inglés), fecha, si está en vigor, versiones consolidadas (con la que rige hoy y las futuras) y actos que lo modifican, con enlaces a EUR-Lex y al DOUE (ELI). Acepta la cita tal como se escribe ("Reglamento (UE) 2016/679", "Directiva 95/46/CE", "Reglamento (CE) n.º 44/2001"), siglas frecuentes (RGPD, Reglamento de IA, DSA, DMA, Bruselas I bis, Bruselas II bis/ter, Roma I/II/III…) o el número CELEX (32016R0679). No cubre los Tratados ni la Carta de Derechos Fundamentales. Si el acto tiene un nombre usual, viene en "conocido_como": usa solo esos; no añadas apodos de memoria («Roma III», «Bruselas II bis»…) a actos que no lo traigan.

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

Input Schema

NameRequiredDescriptionDefault
normaYesCita, siglas o CELEX del acto.
idiomaNoCastellano ("es", por defecto) o inglés ("en").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, non-destructive), and the description adds real substance on top: the fields returned, the fact that consolidated versions include both current and future ones, and the operational rule that only nicknames present in "conocido_como" may be used, not invented ones. It does not say what happens when the citation resolves to nothing or to multiple acts, which is the main remaining behavioral gap for an open-world lookup.

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?

Front-loaded with purpose and return fields, then input formats, then the scope exclusion and the nickname caveat — a sensible order with no filler sentences. It is dense and parenthetical-heavy, so it reads as slightly crowded, but every clause carries information an agent needs.

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 carries the burden of describing the response and does so thoroughly (title, date, vigencia, consolidated versions, modifying acts, EUR-Lex/DOUE ELI links). Combined with the exclusion of Treaties/Charter and the accepted input forms, an agent has enough to call it correctly; only failure/ambiguity behavior is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description goes well beyond it by illustrating the accepted grammar of "norma" (citation string, acronym, or CELEX such as 32016R0679) with several worked examples. It also confirms the default for "idioma" (Castellano por defecto), reinforcing the enum meaning rather than merely repeating it.

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?

Opens with a specific resource and scope ("Ficha de un reglamento, directiva o decisión de la UE") and enumerates exactly what the record contains: official title, date, in-force status, consolidated versions, amending acts, EUR-Lex/DOUE links. It also carves out a boundary ("No cubre los Tratados ni la Carta"), which separates it from general EU search tools like ue_buscar_normas.

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 concrete when-to-use signals by listing the accepted input forms — literal citation ("Reglamento (UE) 2016/679"), common acronyms (RGPD, DSA, DMA, Bruselas I bis) and CELEX numbers — plus an explicit exclusion for Treaties and the Charter. It does not name a sibling alternative for the excluded cases (e.g. pointing to ue_buscar_normas or ue_texto_articulo), which keeps it short of a 5.

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