Skip to main content
Glama

Japan Diet: observed bill changes since a date

jp_diet_changes
Read-only

Which Diet bills moved since a date? Changes this service observed on the bill pages of both houses, newest first: bill id and title, from-stage and to-stage (or list status before and after), the published date of the new stage, when observed, and the source URL. First loads and loading of past sessions are not counted. 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_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of changes, 1-500 (default 200)
sinceNoJapan date YYYY-MM-DD; changes observed on or after it (default: 7 days ago)

Output Schema

NameRequiredDescriptionDefault
noteYes
queryYes
termsYesURL of the terms of service.
totalYes
sourceYes
statusYes
changesYes
truncatedYes
disclaimerYes
provenanceYesFreshness receipts for every upstream source used.
answered_atYes
attributionYes
official_checkYes
unknown_reasonYes
observation_noteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real behavior beyond that — result ordering (newest first), the exact fields returned, and the exclusion of initial/past-session loads. It also states 'Free', clarifying there is no metering cost, which matters for an open-world external service.

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 question, then a compact field list. The middle clause enumerating every returned field is somewhat dense, but each element conveys real information and there is no filler.

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?

For a two-parameter, read-only, open-world listing tool with an output schema present, the definition covers scope, ordering, exclusions, and cost adequately. The one remaining ambiguity — whether 'since' filters by observed-at time versus published stage date — is partly clarified by the returned-field list but not resolved outright.

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 description coverage is 100%: both 'limit' (1-500, default 200) and 'since' (YYYY-MM-DD, default 7 days ago) are fully documented in the schema. The description reinforces the date semantics but adds no syntax or edge-case detail beyond what the schema already supplies, so the baseline of 3 applies.

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?

Opens with a specific framing ('Which Diet bills moved since a date?') and then names the exact resource and scope: changes observed on the bill pages of both houses, newest first. That scoping ('moved' / 'changes observed') distinguishes it cleanly from a static status or list tool such as jp_diet_bill_status or jp_diet_bills_list.

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 rather than stated: an agent can infer it should call this to poll for movement after a given date, and the note that 'first loads and loading of past sessions are not counted' usefully bounds the expected results. However, there is no explicit when-to-use/when-not guidance and no named alternative for adjacent needs like looking up a current bill status.

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