Skip to main content
Glama

Merit — Ukrainian Law & Registers

List Provision Editions

ua_law__get_unit_editions
Read-onlyIdempotent

The editions on which one unit's text changed, and what changed it.

Each entry is a version: its dated urn, how many editions kept it, and amended_by, the acts behind the change ('unit_notes': cited by the unit's notes; 'edition_basis': the edition's basis). removed: the unit disappears; moved_from: its address changed (text_changed false if only that). A baseline opens the list: the first text, or with from_date the text in force that day. Edition '30000101' and up (edition_date null) takes effect on a date not yet fixed.

complete: false means limit cut older entries.

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": {
      "urn": "<urn>"
    },
    "name": "ua_law__get_unit_editions"
  }
}

Input Schema

NameRequiredDescriptionDefault
urnYesUnit URN, from get_document_toc.
limitNoEditions to read text for, newest first.
to_dateNoLatest edition, inclusive.
from_dateNoEarliest edition, inclusive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, and the description adds real behavior beyond that: entries carry amended_by with its two provenance sources, 'removed'/'moved_from' flags, and the special meaning of edition '30000101' (not-yet-fixed effective date). It also exposes the truncation signal (`complete: false` means limit cut older entries), which an agent cannot infer from annotations alone.

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 the core purpose and then field-by-field explanation; no filler sentences. The telegraphic fragments ("`removed`: the unit disappears") are compressed almost to the point of ambiguity, which slightly hurts parseability but not economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return shape, which it does for urn, amended_by, removed, moved_from, baseline, and complete. However, the type and format of `urn`, how many editions exist, and the meaning of 'how many editions kept it' remain underspecified for a tool whose whole output is these entries.

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 is 3, but the description adds meaning the schema does not: from_date changes the baseline to the text in force that day, and limit's truncation is surfaced through `complete`. It does not explain to_date's interaction with the baseline or date format, so it stops short of full compensation.

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?

The description states a specific resource and scope: the editions on which one unit's text changed, plus what changed it, keyed by a unit URN. It is clearly distinct from get_unit (current text) and get_document_toc (structure), though it never names those siblings to route the agent explicitly.

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?

Usage is implied rather than stated: from_date/to_date select a range, and the baseline entry is defined as the text in force on from_date. There is no explicit 'use this instead of X' guidance or stated prerequisite beyond the schema note that urn comes from get_document_toc.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.