Skip to main content
Glama

list_law_revisions

Read-onlyIdempotent

List revisions for a law ID with optional inclusive effective-date filters to track amendments and version history.

Instructions

List revisions by law ID, optionally filtering by inclusive effective dates.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
law_idYes
offsetNo
effective_toNo
effective_fromNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral detail — that effective date bounds are inclusive — but says nothing about ordering, pagination behavior, or what happens when effective_from is null.

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?

A single front-loaded sentence with zero filler; the required key (law ID) comes before the optional filter, matching the argument priority.

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 annotations covering safety and an output schema covering return shape, the definition is close to sufficient for this simple list tool. The remaining gap is pagination semantics (limit default 10, max 100, offset cap), which an agent would want spelled out.

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 0%, so the description must carry the param burden; it clarifies law_id and both date parameters, including their inclusive boundary semantics, which is real added meaning. However, limit and offset (pagination) are never mentioned, leaving two of five parameters unexplained anywhere.

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 gives a specific verb ('List') and resource ('revisions'), scoped by law ID, which is distinguishable from the siblings (get_law_article, get_law_text, search_law_text, search_laws) since none of those list revisions. It stops short of explicitly naming a sibling it complements, but the purpose is unambiguous.

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?

'Optionally filtering by inclusive effective dates' implies when the date parameters matter, but there is no statement of when to prefer this over get_law_text or search_laws, and no prerequisites or exclusions are given. Usage must be inferred from the one clause about optional filtering.

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