Skip to main content
Glama

Japan: one law's amendments and enforcement dates

jp_diet_law_history
Read-only

How has this Japanese law been changed, by which Acts, and from when? Give an e-Gov law id (e.g. 322AC0000000049 = 労働基準法). Returns amendments by Acts since 1998 that e-Gov's revision history lists (mostly from 2016-2017 on), newest first: amending law number and title, promulgation date, each enforcement stage with its date (future included) and e-Gov's note, e-Gov link, and the Diet bill id when known. No law text. Free.

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

Input Schema

NameRequiredDescriptionDefault
law_idYese-Gov law id, for example 322AC0000000049

Output Schema

NameRequiredDescriptionDefault
lawYes
noteYes
queryYes
termsYesURL of the terms of service.
statusYes
changesYes
coverageYesHow far this service has read e-Gov's revision histories.
answered_atYes
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses real behavioral limits: coverage begins with what e-Gov's revision history lists, is mostly 2016-2017 onward, is ordered newest first, and excludes law text. It also flags that enforcement stages may be in the future. The lack of any note on coverage gaps for older amendments or result caps keeps it from a 5.

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?

It opens with the user question the tool answers, then front-loads the input format before enumerating return fields. The output enumeration is a single dense run-on sentence, but no sentence is wasted and 'No law text. Free.' efficiently closes the scope.

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?

For a single-parameter read tool with an output schema, this covers everything an agent needs: input format, an example, what is returned per amendment and per enforcement stage, ordering, data-source coverage, and an explicit content exclusion.

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 coverage is 100%, and the schema already supplies the pattern and the example id 322AC0000000049. The description adds only the human-readable mapping of that id to 労働基準法, which is marginally useful but largely restates structured data, so the baseline of 3 applies.

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 verb and resource: it returns a Japanese law's amendment history, naming the amending Acts, promulgation dates, and each enforcement stage. It also scopes itself explicitly with 'No law text.' It falls short of a 5 only because it never distinguishes itself from the similarly themed sibling jp_diet_enforcement_calendar.

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 establishes the triggering condition (the user asks how a law changed, by which Acts, and from when) and the required input form, including a worked e-Gov law id mapping to 労働基準法. It supplies no explicit exclusions or alternative-tool routing against jp_diet_enforcement_calendar, so the agent must infer the boundary.

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