Skip to main content
Glama

japanlaw.org — Japanese law

Search Japanese law

search
Read-onlyIdempotent

日本の法令についての質問(有給休暇、解雇予告、留学生のアルバイト、在留資格、確定申告など)に、根拠となる条文を探す。 Find what Japanese law says on a question asked in words — paid leave, notice of dismissal, a student's part-time work, 有給休暇, 解雇予告 — and the provisions to quote and link. Search the Japanese statutes japanlaw.org holds, in force today. A query with any Japanese in it searches the Japanese text (時間外労働, 有給休暇); one without searches the English shown for each provision, stemmed (overtime, paid leave). Results are the laws whose names or descriptions match — as many as limit, lawsTotal counting them all — then one result per matching article at its best-matching paragraph or item, best first; each has an id to pass to fetch (or pass its law and path to get_provision as law and address), the page's url, the Japanese and English designation (第三十六条第一項 / Article 36, paragraph (1)) and a snippet. terms lists words a law defines that match; concepts, words of Japanese law the site explains. Every word must be at least two characters. Only the laws list_laws names are searched; law searches one of them alone, its provisions and the terms it defines. When a law the reader names finds nothing, check list_laws: one not there is not held — say so rather than answering from memory.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawNoSearch this law only: its Japanese title, English title, short name, slug or e-Gov law ID. Unset searches every law held.
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.
pageNoWhich page of results, from 1.
limitNoArticles per page, 1–25; default 10. As many laws at most come first.
queryYesWords to find, in Japanese or English.

Output Schema

NameRequiredDescriptionDefault
pageYes
pagesYes
totalYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Articles per page, 1–25; default 10."New value: +"Articles per page, 1–25; default 10. As many laws at most come first."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: result ordering, lawsTotal, one result per matching article at its best-matching paragraph/item, snippet and designation fields, terms and concepts, and the fallback to list_laws. Annotations already cover read-only/idempotent safety, and the description does not contradict them.

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?

The key purpose and usage rules are front-loaded, and most sentences carry useful operational detail. It is long and includes bilingual example repetition, but the complexity of the search semantics justifies most of the length.

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?

Given five parameters, an output schema, and rich annotations, the description is complete enough for an agent to invoke it correctly. It covers query language behavior, law scoping, result structure, and the list_laws fallback.

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 meaning: Japanese-containing queries search Japanese text, non-Japanese queries search stemmed English text, every word must be at least two characters, and the law parameter restricts searching to one named law.

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 action and resource: finding Japanese statutory provisions for natural-language questions, with concrete examples. It also distinguishes itself from sibling tools by explaining that result ids are passed to fetch or get_provision.

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?

Explains when to use this tool, how Japanese versus English queries behave, and what to do when a named law returns nothing: check list_laws and say the law is not held rather than answer from memory. It also names related tools for next steps.

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