Skip to main content
Glama

Japan Diet: bill statistics by session and kind

jp_diet_stats
Read-only

Counts of law bills per Diet session and kind (cabinet / member bills): listed, newly submitted, carried in, enacted, withdrawn, not concluded, carried over, rejected, enactment share of closed sessions; days from submission to enactment (median, p25, p75, n); by committee. This service's own aggregation of the bill pages it has loaded, always with coverage (which sessions are complete or still loading). Past facts only, not a forecast. 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_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOnly this bill kind: 閣法 or cabinet, 衆法 or hr_member, 参法 or hc_member
sessionNoOnly this Diet session (default: every loaded session)

Output Schema

NameRequiredDescriptionDefault
queryYes
termsYesURL of the terms of service.
sourceYes
statusYes
totalsYes
coverageYes
sessionsYes
disclaimerYes
provenanceYesFreshness receipts for every upstream source used.
answered_atYes
attributionYes
computed_atYes
definitionsYes
by_committeeYes
official_checkYes
unknown_reasonYes
observation_noteYes
days_to_enactmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses provenance ('this service's own aggregation of the bill pages it has loaded'), a coverage caveat (which sessions are complete or still loading), and a scope limit ('past facts only, not a forecast'). It does not state how incomplete sessions are represented in the output, which is the main remaining behavioral gap.

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?

Front-loaded with the core purpose, then a compact semicolon list of metrics and caveats — dense but every clause carries information. The metric enumeration is long, but it substitutes for the output schema rather than padding.

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?

With only two optional parameters and an output schema present, the description covers scope, dimensions, and data-quality caveats adequately. The one thing an agent might still want — what a partial-coverage result looks like numerically — is left unstated, but it is minor for a read-only stats tool.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters and the kind enum are already fully documented in the schema. The description repeats the cabinet/member grouping for `kind` but adds no format or defaulting detail beyond what the schema states, so baseline 3 applies.

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 first sentence names a specific verb and resource ('Counts of law bills per Diet session and kind') and enumerates the exact measures produced (listed, submitted, enacted, duration percentiles, by committee). This clearly separates it from bill-level siblings like jp_diet_bills_list, though it never names an alternative explicitly.

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?

Usage is implied by the metric inventory: an agent deduces this is for aggregate statistics rather than individual bill retrieval. There is no explicit when-to-use/when-not guidance or pointer to a sibling for per-bill data, so the agent must infer routing from the metric list alone.

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