japan-law-util-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load_guidelineA | Usage guideline for the Japanese law tools: how to find a law, read its articles by elm, search the text of every law, pin a point in time, what e-Gov法令検索 covers, and the conditions of use. Read it before your first search. |
| search_lawsA | Find Japanese laws (acts, cabinet orders, ministerial ordinances) by title, law number, type, subject category or promulgation date. Returns one page of laws with each law's law_id, law number, enforcement date, repeal status and e-Gov URL; total_count and next_offset tell whether more pages exist. Use the law_id with the other tools. |
| search_law_textA | Search the text of every Japanese law for a keyword and get the laws it appears in with the matching sentences, each hit marked with 【】. The keyword may be a search expression: space for AND, | for OR, ! to exclude, () to group, or * and ? as wildcards (wildcards cannot be combined with the operators). scan_limit counts hit positions scanned, not laws; lower hits_per_law and raise scan_limit to see more laws. |
| list_law_revisionsA | List one law's amendment history: each revision's enforcement date, the amending law, its revision id and whether that revision is in force now, not yet in force or repealed. Use it to choose the asof date or revision id to read, or to see when a change takes effect. |
| get_law_outlineA | Get one law's table of contents: every part, chapter, section, article (with its caption), supplementary provision and appendix, in order, each with the elm value that reads it with read_law_text. Read this before reading a long law, and pass the elm it gives rather than building one yourself. Call read_law_text with the same include_amendment_supplements, which changes which supplementary provisions each elm names. Paged with offset. |
| read_law_textA | Read a law's text as plain text: the whole law, or the one part elm names, such as MainProvision-Article_17, MainProvision-Chapter_4-Section_2, SupplProvision[1]-Article_1 or AppdxTable[1]. The text comes back in pieces of max_chars; continue from next_offset. The law's 目次 is not included — get_law_outline returns it — and the supplementary provisions of amending laws are left out unless include_amendment_supplements is true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a clearly distinct operation: metadata search, full-text search, revision history, table of contents, article text reading, and usage guidance. The only potentially similar pair, search_laws and search_law_text, is explicitly separated by metadata vs. full-text search behavior.
All tool names follow a consistent snake_case verb_noun pattern such as search_laws, list_law_revisions, get_law_outline, and read_law_text. The minor singular/plural variation between law and laws is natural and does not break predictability.
Six tools is well-scoped for a read-only Japanese law research server. Each tool has a clear role in the workflow and no redundant tools appear to be present.
The surface covers the full research lifecycle: onboarding guidance, law discovery, full-text search, revision history, structural outline, and detailed text reading. It also handles pagination and point-in-time/revision selection, leaving no obvious dead ends for the stated domain.