Hourei 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_lawC | 法令名や法令番号で法令を検索します。キーワード検索に対応しています。 |
| get_law_dataC | 法令番号を指定して法令の詳細データを取得します。 |
| get_law_revisionC | 法令の改正履歴を取得します。 |
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 3 tools
Each tool has a clearly distinct purpose: get_law_data retrieves detailed data for a specific law, get_law_revision fetches amendment history, and search_law performs keyword-based searches. There is no overlap in functionality, making tool selection unambiguous.
All tools follow a consistent verb_noun naming pattern (get_law_data, get_law_revision, search_law) using snake_case. The naming is predictable and readable, with no deviations in style.
With only 3 tools, the set feels thin for a law-related server, potentially lacking operations like creating, updating, or deleting laws. However, it covers basic retrieval and search functions adequately for a minimal scope.
The tools provide search and retrieval capabilities but lack full CRUD coverage (e.g., no create, update, or delete operations). This is a notable gap for managing laws, though agents can work with the available read-only functions.