Skip to main content
Glama

Japan Law Get Article

japan_law_get_article
Read-onlyIdempotent

Fetch a single article of a Japanese law by law id + article number, e.g. law_id "415AC0000000057" (個人情報保護法) + article "27" for 第二十七条. Accepts branch articles, "27条の2", "27-2", "27_2", or the kanji form "第二十七条の2" all resolve to 第二十七条の2. Returns just that article's caption, heading, and text (not the whole law, use this instead of get_law when you know the article you want). Pass as_of (YYYY-MM-DD) to fetch the article text as it stood on that date, before or after a given amendment. Source: e-Gov 法令検索.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "law_id": "415AC0000000057",
      "article": "27"
    },
    "name": "japan_law_get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoPoint-in-time date (YYYY-MM-DD). Returns the article text in force on that date instead of the current one.
law_idYese-Gov law id, e.g. "415AC0000000057".
articleYesArticle number: "27", "27条の2", "27-2", "27_2", or kanji "第二十七条の2".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already cover safety and idempotency (readOnly, destructive=false, idempotent, openWorld), so the description's job is to add context — and it does: scoped return payload ('just that article's caption, heading, and text'), point-in-time retrieval semantics, and the data source (e-Gov). It does not say what happens for a nonexistent article or branch, which keeps it below 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.

Conciseness5/5

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

The core action and its law/article inputs are front-loaded, followed by the disambiguation from get_law and the as_of modifier. The example values are dense but each one resolves a real formatting ambiguity rather than padding.

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?

No output schema exists, yet the description states exactly what is returned (caption, heading, text, not the whole law). Combined with the sibling routing rule and format-normalization guidance, an agent has everything needed to call it correctly on the first attempt.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 earns more by documenting resolution behavior the schema does not: that '27条の2', '27-2', '27_2', and '第二十七条の2' all normalize to the same branch article. It also clarifies as_of works both before and after a given amendment.

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 verb and resource — 'Fetch a single article of a Japanese law by law id + article number' — and concretely scopes it to one article rather than a whole law. The explicit contrast with get_law makes it distinguishable from the sibling without opening either 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?

Gives an explicit routing rule: 'use this instead of get_law when you know the article you want.' It also names the condition for the alternative mode (supply as_of to fetch text as of a date), leaving nothing to inference.

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.