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

Consulta Boletines Oficiales - Legislación consolidada

euskadi_texto_norma

Read-only

Retrieve the full text, validity status, and cross-references of a specific BOPV regulation from Open Data Euskadi using the act ID returned by the Basque regulation search.

Instructions

Texto completo, vigencia y referencias cruzadas de una disposición concreta del BOPV (Open Data Euskadi), a partir del id que devuelve euskadi_buscar_normativa (formato "AAAA/MM/N").

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": "euskadi_texto_norma"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId del acto, formato "AAAA/MM/N", p. ej. "2024/7/3154".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish the safe-read profile (readOnlyHint=true, destructiveHint=false), and the description adds the genuinely useful disclosure that the payload includes vigencia and cross-references, not just raw text — important since there is no output schema. It doesn't note anything about legal-text caveats, language variants, or response size for long laws.

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?

A single dense sentence that front-loads the returned content and pushes the input requirement to the end; every clause carries information. The '(Open Data Euskadi)' gloss is the only near-redundant fragment.

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 takes on the burden of describing returns and does so by naming the three content components. What's missing is behavior for edge cases (id not found, extremely long texts) — minor for a single-required-param read tool.

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 parameter description already gives the 'AAAA/MM/N' format with an example. The description only adds provenance (the id comes from the search tool), which is modest value beyond the schema, so the 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 retrieval action over a well-defined resource (a concrete BOPV disposition) and enumerates exactly what comes back: full text, in-force status, and cross-references. It also names the sibling that produces the required input, distinguishing it cleanly from euskadi_buscar_normativa.

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?

Implies the workflow clearly: this is the follow-up call once you have an id from euskadi_buscar_normativa, and the id format requirement is restated. It stops short of stating a 'when not to use' case or what to do when the id is unknown, so it falls 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.