Skip to main content
Glama

search_law_text

Read-onlyIdempotent

Find keyword occurrences in Japanese law text and return matching positions across laws, with optional filters for law number, reference date, and result limits.

Instructions

Find keyword occurrences in law text. The limit counts matching positions across laws.

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": {
      "keyword": "<keyword>"
    },
    "name": "search_law_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo
limitNo
offsetNo
keywordYes
law_numberNo
sentence_text_sizeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish a read-only, idempotent, non-destructive, open-world operation. The description adds the non-obvious behavior that limit counts matching positions across laws, but it does not explain matching semantics, result ordering, or how offset interacts with that limit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences front-load the operation and then state a useful, non-obvious limit rule. There is no filler, repetition, or unnecessary structural overhead.

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?

The output schema and annotations cover return shape and safety, but the description is insufficient for reliably using most of this six-parameter interface. Historical-as-of behavior, law filtering, pagination, and snippet sizing are all left to inference, so only the basic keyword-search invocation is well supported.

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?

With 0% schema description coverage, the description needs to compensate, yet it explains only limit beyond the structured schema. The keyword's broad role is implied, while as_of, law_number, offset, and sentence_text_size remain unexplained, including whether law_number restricts scope and what text size controls.

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 states a specific action and resource: finding keyword occurrences in law text, which clearly conveys occurrence-level search. It does not explicitly distinguish the tool from siblings such as search_laws or get_law_text.

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

Usage Guidelines3/5

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

The wording implies using the tool to locate keyword matches within legal text, and the cross-law limit rule suggests corpus-wide searching. It provides no explicit selection criteria, prerequisites, or guidance about when to use search_laws, get_law_text, or get_law_article instead.

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