Skip to main content
Glama

Japan: law enforcement calendar

jp_diet_enforcement_calendar
Read-only

Which Japanese laws change on which dates? Enforcement dates of amendments, new laws and repeals made by Acts between two dates (Japan time; default the next 365 days; the last year also works): law changed (e-Gov id, title, number, category), amending law number and title, promulgation date, date and its basis, e-Gov's note on the provision, e-Gov link, and the Diet bill id when known. From e-Gov law search (PDL1.0). Facts only. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jp_diet_enforcement_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast date, YYYY-MM-DD (default from + 365 days; at most 731 days after from)
fromNoFirst date, YYYY-MM-DD in Japan time (default today)
limitNoMaximum number of dated entries, 1-500 (default 500)
include_undatedNotrue: also list revisions whose enforcement date is not set yet (default false)

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, but the description adds real context: the data comes from e-Gov law search under PDL1.0, results are facts-only, and access is free, plus what the record fields contain. It says nothing about rate limits or pagination beyond the schema's limit, so it is not fully complete.

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?

The purpose is front-loaded in the first clause, which is good, but the rest is a dense comma-run of parentheticals and a long return-field list that duplicates the output schema. The trailing 'Facts only. Free.' is promotional filler that does not help an agent invoke the tool.

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 an output schema, full annotation coverage and 100% parameter coverage, the description only needs to set scope and provenance, which it does: date window, Japan-time zone, e-Gov source and licensing. Nothing an agent needs to call it correctly is conspicuously missing.

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%, so from and to, limit and include_undated are already documented. The description reinforces Japan-time semantics and the 'last year also works' range hint, but it adds no syntax, boundary or interaction detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource: it returns enforcement dates of amendments, new laws and repeals made by Acts within a date window, and enumerates the fields returned. That is far more specific than the name alone. It does not, however, distinguish itself from the potentially overlapping sibling jp_diet_changes, so an agent must infer the boundary.

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?

Gives clear operating context: dates are Japan time, the window defaults to the next 365 days, the past year also works, and undated revisions are excluded unless asked for. No explicit when-not-to-use condition or named alternative is provided, which keeps it below a 5.

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