Skip to main content
Glama

japanlaw.org — Japanese law

See what amendments changed

get_amendments
Read-onlyIdempotent

What an amendment to a Japanese law changes, and when; for what changes across every law between two days, list_changes. A law's amendments whose changes japanlaw.org holds: the amending Act (titles, law number), the day it takes effect, whether it is in force, not yet in force or since replaced (state), how many provisions it changes, adds and removes, and its version — the text it leaves, which get_provision and fetch read where textHeld is true. With version — {"law": "labor-standards-act", "version": "20270401_508AC0000000060"} — every provision that amendment changes, its wording before and after in Japanese and English, and whose each English is (beforeEnglishWhose, afterEnglishWhose). A long one stops at a provision; continued.cursor, passed back as cursor with the same version, goes on. An amendment e-Gov publishes no text for is named as such (comparedAcross, textPublished false): its changes are listed with the next amendment's and cannot be told apart from them — never describe them as its own. One whose changes are not held says so; never describe its changes from memory. Link each amendment by its url.

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

Input Schema

NameRequiredDescriptionDefault
lawYesThe law: its Japanese title (労働基準法), English title (Labor Standards Act), short name (労基法), slug (labor-standards-act) or e-Gov law ID (322AC0000000049).
langNoThe language of the pages every url opens, and of the card get_provision is drawn as: "en" (default) or "ja". The text returned always holds both languages.
cursorNoGo on from here: the cursor an earlier answer's continued gave, with the same version.
versionNoOne amendment, by the version a list gave (20270401_508AC0000000060) — the text it leaves, as get_provision and fetch take it: its changes, provision by provision. Unset lists the amendments.

Output Schema

NameRequiredDescriptionDefault
lawIdYes
lawSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Go on from here: the cursor an earlier answer's continued gave, with the same version.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • removedInput schema / properties / from
      Removed value: -{
      -  "description": "Go on from this provision: the from an earlier answer's continued gave, with the same revision.",
      -  "maxLength": 200,
      -  "type": "string"
      -}
    • removedInput schema / properties / revision
      Removed value: -{
      -  "description": "One amendment, by the revision key a list gave (20270401_508AC0000000060): its changes, provision by provision. Unset lists the amendments.",
      -  "maxLength": 80,
      -  "minLength": 1,
      -  "type": "string"
      -}
    • addedInput schema / properties / version
      Added value: +{
      +  "description": "One amendment, by the version a list gave (20270401_508AC0000000060) — the text it leaves, as get_provision and fetch take it: its changes, provision by provision. Unset lists the amendments.",
      +  "maxLength": 80,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, closed-world), it discloses pagination behavior (continued.cursor replayed with the same version), a significant data caveat (amendments with textPublished false have their changes merged with the next amendment's and cannot be told apart), and a coverage warning that some amendments' changes are not held. These are non-obvious traits the annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the prose is telegraphic and clause-stacked ("its version — the text it leaves, which get_provision and fetch read where textHeld is true"), which slows parsing of an otherwise informative definition. Almost every sentence carries real content, but the em-dash nesting hurts readability.

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

Completeness5/5

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

Covers the full call lifecycle for a moderately complex tool: list mode vs. single-amendment mode, pagination continuation, and two distinct data-availability failure modes. An output schema exists, yet the description still supplies the interpretive caveats an agent needs to avoid misattributing changes.

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; the description still adds value by spelling out what passing a version yields (per-provision before/after wording in Japanese and English, plus beforeEnglishWhose/afterEnglishWhose) and by linking cursor to continued.cursor from the same version. It does not explain the law identifier forms or the lang parameter, leaving those entirely to the schema.

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 resource and scope: what a single amendment to a Japanese law changes, when it takes effect, and its state. It explicitly contrasts itself with list_changes (cross-law, date-range) and with get_provision/fetch (text reading), so an agent can route without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative and the condition that selects it: "for what changes across every law between two days, list_changes." It also gives an explicit usage rule for the version parameter ("Unset lists the amendments") and a prohibition against answering from memory, which is exactly the routing guidance an agent needs.

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.

Resources