Skip to main content
Glama

search_laws

Read-onlyIdempotent

Search Japanese laws by title to find matching legislation, optionally as of a specific date (YYYY-MM-DD) to retrieve the version in effect at that time.

Instructions

Search by Japanese law title, optionally as of a date (YYYY-MM-DD).

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": {
      "title": "<title>"
    },
    "name": "search_laws"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo
limitNo
titleYes
offsetNo

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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds the 'as of a date' framing, which explains the point-in-time semantics of a lookup, but says nothing about how titles are matched or how results are ordered and paged.

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?

A single short sentence with the resource front-loaded and no filler. It is efficient, though its brevity is partly under-specification rather than pure concision.

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, but for a four-parameter search tool with zero schema descriptions the definition leaves pagination and matching behavior unspecified. An agent cannot tell from the definition whether paging is expected or how title lookups behave.

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 four parameters, so the description must compensate, yet it only touches title and as_of and gives as_of merely a format hint. The limit and offset parameters are entirely unexplained, and the title matching rule (exact, partial, case-sensitive) is never stated.

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 verb and resource, 'Search by Japanese law title,' and scopes it geographically to Japanese law, which separates it from siblings like search_law_text and get_law_article. It stops short of naming an alternative explicitly, so the differentiation is implicit rather than stated.

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 when-to-use or when-not-to-use guidance and no reference to the sibling tools. An agent must infer that this is a title lookup rather than a full-text or article retrieval tool purely from the word 'title'.

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