Skip to main content
Glama

Japan Diet: law bills of a session

jp_diet_bills_list
Read-only

List the law bills of a Diet session (default: current; past sessions from 142 (1998) as loaded, see jp_diet_sessions_list; 閣法 = cabinet bills, 衆法/参法 = member bills of the House of Representatives/Councillors) with where each is now: status as published (審議状況, e.g. 成立 = enacted), a status code, the position read from published stages (e.g. in_committee), latest stage date and source URLs. Filters: session, house, kind, status, title words. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jp_diet_bills_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoBill kind: 閣法 or cabinet (cabinet bill), 衆法 or hr_member (House of Representatives member bill), 参法 or hc_member (House of Councillors member bill)
houseNoOnly bills now with this house, according to the published status
limitNoMaximum number of bills, 1-200 (default 100)
queryNoWords in the bill title, in Japanese (for example 消費税 = consumption tax)
statusNoOnly bills with this status code (see status_meaning in the answer)
sessionNoDiet session number, for example 222 (default: the current session)

Output Schema

NameRequiredDescriptionDefault
billsYes
queryYes
termsYesURL of the terms of service.
totalYes
sourceYesWhere the answer comes from and how fresh it is.
statusYes
truncatedYes
disclaimerYes
provenanceYesFreshness receipts for every upstream source used.
answered_atYes
attributionYes
status_noteYes
official_checkYes
unknown_reasonYes
session_coverageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real behavior beyond that by separating 'status as published' from 'the position read from published stages', telling the agent one field is derived rather than official. It also flags the dataset boundary ('past sessions from 142 (1998) as loaded'), which warns that older or unloaded sessions may be absent. The trailing 'Free.' is ambiguous (no cost? free-text search?) and adds no usable signal.

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

Conciseness3/5

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

The core purpose is front-loaded and every clause carries information, but it is delivered as one long sentence freighted with nested parentheses, which makes it harder to scan than a short purpose sentence followed by filters. The terminal 'Free.' is an unearned fragment that leaves the reader guessing at its meaning.

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?

An output schema exists, so return values need not be spelled out, yet the description still names the key fields, and it covers the two things the schema and annotations cannot: the default session and the historical data boundary. For a read-only list tool with full schema coverage this is close to complete; only ordering/pagination behavior and guidance on single-bill lookups are unaddressed.

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, and the description clears that bar by adding meaning the enum lists do not: it maps the Japanese labels 閣法/衆法/参法 to cabinet vs. member bills and gives 成立 = enacted as a concrete status reading. It also documents the session default and the historical range, which the schema's bare 'default: the current session' only partly conveys.

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

Purpose5/5

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

States a specific verb and resource ('List the law bills of a Diet session') and then enumerates exactly what each record carries: published status (審議状況), a status code, the position derived from published stages, latest stage date, and source URLs. It also glosses the bill kinds, so an agent knows the domain shape without opening the schema, and it points to jp_diet_sessions_list for session numbers, distinguishing it from the session-list sibling.

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?

Gives clear operating context: default is the current session, past sessions are available from 142 (1998) 'as loaded', and the session filter is the lever for history. It enumerates the usable filters (session, house, kind, status, title words). It does not, however, route the agent away from this tool toward a sibling such as jp_diet_bill_status when only one bill's status is needed, so no explicit exclusions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources