egov-law-mcp
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 |
|---|---|
| search_lawsC | Search by Japanese law title, optionally as of a date (YYYY-MM-DD). |
| get_law_articleC | Get a main-provision article by law or revision ID. Use 709 or 709_2 for branches. |
| list_law_revisionsA | List revisions by law ID, optionally filtering by inclusive effective dates. |
| search_law_textB | Find keyword occurrences in law text. The limit counts matching positions across laws. |
| get_law_textC | Read a character page of law XML, optionally selecting a provision or appendix. |
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 5 tools
Each tool has a mostly distinct role: title search, keyword occurrence search, character-page reading, article retrieval, and revision listing. The closest overlap is between get_law_article and get_law_text, but the descriptions distinguish structured article access from XML page reading.
All tool names consistently use snake_case with a clear verb_noun pattern: search_laws, get_law_article, list_law_revisions, search_law_text, get_law_text. The convention is predictable throughout.
Five tools is well-scoped for a focused legal-text retrieval server. Each tool covers a distinct access pattern—search, article retrieval, revision listing, text search, and text reading—without obvious redundancy.
The surface covers the main read-only lifecycle for Japanese law data: discovering laws, inspecting revisions, retrieving articles, searching text, and reading law XML pages. Minor gaps exist around direct law metadata retrieval or batch operations, but core workflows are supported.