Skip to main content
Glama

Read an article

read_legislation_block
Read-only

Retrieve the current wording and in-force status of a consolidated legislation block—article, preamble, annex, or provision—plus later approved text and earlier version history.

Instructions

Read the latest wording of one block of a consolidated rule, and whether it is in force.

A block is an article, the preamble, an annex or a provision. The answer also gives any approved wording that takes effect later, and lists the earlier versions of the block with the rules that introduced them. Check in_force before presenting the text as law.

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": {
      "law_id": "<law_id>",
      "block_id": "<block_id>"
    },
    "name": "read_legislation_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
law_idYesBOE identifier, such as BOE-A-2018-16673.
block_idYesblock_id from the outline of get_legislation.

Output Schema

NameRequiredDescriptionDefault
urlYes
kindYesprecepto, preambulo, parte_final, firma, nota_inicial…
textYesWording of current_version as plain text; empty when there is none. Notes start with 'Nota:'.
titleYes
law_idYes
noticeNoBasado en datos de la Agencia Estatal Boletín Oficial del Estado (https://www.boe.es). Texto consolidado de carácter meramente informativo: solo la versión electrónica firmada del BOE, en PDF, es oficial y auténtica.
block_idYes
in_forceYesTrue only when the rule is in force and `text` has taken effect. A repealed rule keeps its last wording, which is no longer in force.
truncatedYesTrue when a text was cut to keep the answer short.
law_statusYesStatus of the whole rule today.
upcoming_textNoWording of the soonest upcoming version, if there is one.
current_versionYesLatest version that has taken effect; null when the block only has wording that takes effect later.
previous_versionsYesVersions no longer in force, oldest first.
upcoming_versionsYesApproved wordings that take effect after today, soonest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes further by disclosing the response shape: current wording, in-force status, any approved wording that takes effect later, and earlier versions with the rules that introduced them. It also flags a correctness caveat (check in_force) that guards against presenting superseded text as law. It stops short of noting size, truncation, or error behavior for unknown block_id values.

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?

Four short sentences, front-loaded with the core action, then the definition, then the return contents, then the safety caveat. The middle definition sentence earns its place by resolving an undefined domain term. Minor redundancy between "latest wording" and the version-history sentence, but 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 an output schema present, the description is not obliged to enumerate return fields, yet it usefully sketches them and adds the in-force caveat an agent needs to answer legal-text questions responsibly. Combined with 100% schema coverage on two simple parameters and existing annotations, it is nearly complete; only the get_legislation handoff is stated solely in the schema.

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 both parameters are documented there, including the BOE identifier format and the instruction to source block_id from get_legislation's outline. The description adds no further meaning about either parameter beyond that, which is the baseline expectation when the schema does the work.

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 both a specific verb and resource ("Read the latest wording of one block of a consolidated rule") and defines the ambiguous term by enumerating what a block is (article, preamble, annex, provision). This makes the scope of the read unambiguous. It does not explicitly contrast with get_legislation, which only appears in the schema's block_id hint, so sibling differentiation is implied rather than stated.

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?

Gives one concrete usage rule: check in_force before presenting the text as law. It also implicitly signals this is the tool for retrieving a single block's current text. However, it never says when to prefer this over get_legislation or search_legislation, nor 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.