Skip to main content
Glama
Sign In
e-Gov Law MCP Server

e-Gov Law MCP Server

by ymadd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_article

Retrieve specific provisions from Japanese law by providing a law ID and article number. Optionally add a paragraph number to get a single paragraph or leave blank for the full article.

Instructions

特定の条文を取得します。法令IDと条番号を指定して、特定の条文を取得できます。

使用例:

  • 民法第1条を取得: law_id="129AC0000000089", article="第一条"

  • 民法第2条第2項を取得: law_id="129AC0000000089", article="第二条", paragraph=2

条番号の指定方法:

  • 漢数字: "第一条", "第二十条", "第百二十三条"

  • アラビア数字: "1", "20", "123"

主な法令ID:

  • 民法: 129AC0000000089

  • 会社法: 417AC0000000086

  • 個人情報保護法: 415AC0000000057

  • 下請法: 331AC0000000120

  • 消費者契約法: 412AC0000000061

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": {
      "law_id": "<law_id>",
      "article": "<article>"
    },
    "name": "get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
law_idYes法令ID (例: "129AC0000000089")
articleYes条番号 (例: "第一条", "1")
paragraphNo項番号 (省略時は全項を取得)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It explains the retrieval behavior and paragraph selection via examples, but does not describe return format, error cases, or any special behavior. For a simple read operation this is adequate but not rich.

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 description is well-structured with usage examples, article format guidance, and a law ID list, all relevant to invocation. It repeats the core statement twice at the start, which is a minor inefficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read-only tool with no output schema, the description is sufficiently complete: it covers all parameters, gives examples, and includes authoritative law ID values. A return-format note would be nice but is not essential for correct invocation.

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 adds meaningful value by explaining article number formats (漢数字/アラビア数字) and providing a list of common law IDs, which helps an agent construct valid parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action (取得) and resource (条文) with law_id and article number. It is distinguishable from search_laws and get_law_text by its focus on a specific article, but it does not explicitly contrast itself with those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides concrete usage examples and conditions: use it when you know the law_id and article number. It does not mention exclusions or alternatives, but the examples make the intended use case clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools