Skip to main content
Glama

Rule status, outline and changes

get_legislation
Read-only

Fetches a consolidated Spanish law’s current status, outline, and later amendments (most recent first) to help you review legal changes and locate block IDs for article-level reading.

Instructions

Describe one consolidated rule: its status today, its outline and its later changes.

Later changes come most recent first. Use the outline's block_id with read_legislation_block to read an article.

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

Input Schema

NameRequiredDescriptionDefault
law_idYesBOE identifier, such as BOE-A-2018-16673.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
rankYes
scopeYes
titleYes
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.
statusYes
eli_urlNoEuropean Legislation Identifier.
enactedNoDate of the rule itself.
outlineYes
subjectsYesSubject terms assigned by the BOE.
publishedYes
departmentYes
repeal_dateNoSet when the rule is repealed or will be on that date.
last_updatedYesLast update of the consolidated text (UTC).
in_force_fromNo
later_changesYesMost recent changes first, capped; later_changes_total says how many exist.
official_numberNo
later_changes_totalYes
consolidation_statusYesWhether the BOE has finished consolidating it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds genuine behavioral context beyond that: changes come most recent first, and the outline carries block_id values used for follow-up reads. It says nothing about behavior for an unknown or malformed law_id, which keeps it out of the top band.

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?

Two short sentences plus a follow-up line, with the core purpose front-loaded and zero redundant phrasing. Every clause carries information the 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?

For a single-parameter lookup with an output schema, the description covers the three content sections returned and the natural next step for reading article text. It omits practical limits such as response size or whether the changes list is truncated, which would matter for a consolidation document but does not block correct invocation.

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 the single law_id parameter is documented there with a format example (BOE-A-2018-16673). The description adds no further meaning about the parameter, so the baseline 3 applies; block_id is a returned value, not an input, and does not count here.

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?

The description names a specific verb and resource — 'Describe one consolidated rule' — and enumerates exactly what is returned: status today, outline, and later changes. It also draws a boundary against the sibling read_legislation_block, so an agent can distinguish the two without opening either schema.

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?

It gives a concrete follow-up path: take block_id from the outline and call read_legislation_block to read an article, which tells the agent when to chain rather than attempt a read here. It stops short of explicit exclusions (e.g., when to prefer search_legislation or get_daily_summary), which is why it is not a 5.

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