Skip to main content
Glama

get_law_article

Read-onlyIdempotent

Retrieve a main-provision article from Japanese laws by law or revision ID, optionally as of a date, to fetch the specific legal text you need.

Instructions

Get a main-provision article by law or revision ID. Use 709 or 709_2 for branches.

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_law_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo
law_idYes
articleYes

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 behavior, so the safety profile is covered. The description adds real context beyond that: it returns a 'main-provision' article rather than branch material, and law_id may be either a law or a revision identifier. It does not describe versioning semantics of as_of or what happens when an article is absent, which matters for an open-world lookup.

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?

Two sentences, front-loaded with the action and the resource, with no filler. 'Use 709 or 709_2 for branches' is compressed to the point of ambiguity about what a 'branch' is, but nothing is wasted.

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-value description is fairly excused. However, with three parameters at 0% schema coverage and an open-world lookup, leaving as_of and the article pattern unexplained, and offering no contrast with get_law_text or the search siblings, leaves the agent under-equipped to call this correctly.

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%, so the description must carry parameter meaning. It adds value for law_id (law or revision ID, with 709/709_2 as branch forms) but says nothing about the 'article' identifier format or the optional 'as_of' date, which is a temporal/versioning switch the agent cannot infer from an untyped pattern alone.

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?

States a specific verb and resource ('Get a main-provision article'), scoped to retrieval by law or revision ID, which separates it from get_law_text and search_law_text in spirit. It stops short of naming a sibling or explicitly contrasting with full-text retrieval, so differentiation is implied rather than asserted.

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?

The only guidance is a parameter-value hint ('Use 709 or 709_2 for branches'), which tells the agent how to encode a branch law but not when to choose this tool over get_law_text, list_law_revisions, or search_law_text. No prerequisites, no exclusions, no alternative routing.

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