Skip to main content
Glama

get_law_text

Read-onlyIdempotent

Retrieve a paginated character range of Japanese law XML, optionally selecting a provision or appendix by section, section number, and appendix type.

Instructions

Read a character page of law XML, optionally selecting a provision or appendix.

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>"
    },
    "name": "get_law_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo
limitNo
law_idYes
offsetNo
sectionNoall
appendix_typeNo
section_numberNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds that output is raw law XML delivered in character pages, which is useful. It says nothing about page size limits, offset semantics, or how as_of interacts with revisions, which are the behaviors that actually matter here.

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?

One short sentence, front-loaded with the core action and free of filler. Its brevity borders on under-specification rather than bloat, but as a structural matter it is efficient.

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

Completeness2/5

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

An output schema exists, so return values need not be described. However, a 7-parameter, 0%-coverage paginated reader with a point-in-time option leaves the agent guessing about pagination and revision selection, which is the main complexity of this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, so the description must compensate and largely does not. Only 'provision' and 'appendix' loosely gesture at section/section_number/appendix_type; as_of, limit, offset and law_id receive no explanation of format or effect.

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 gives a specific verb and resource: read a character page of law XML. 'Character page' communicates the paginated retrieval model clearly. It does not differentiate itself from get_law_article or search_law_text, and 'optionally selecting a provision or appendix' is too loose to tell an agent which parameter selects which.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus get_law_article (provision-level fetch) or search_law_text (searching). The only implicit guidance is that this is for paged reading, which the agent must infer from 'character page'.

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