Skip to main content
Glama

Japan Diet: one bill's stage and timeline

jp_diet_bill_status
Read-only

Where is this Diet bill now and how did it get there? Give bill_id (e.g. 222-閣法-1 or 222-cabinet-1) or a title. Returns status, position and the timeline per session and house (referral, committee and plenary decisions, promulgation), each with date, source URL and first observed time; the Diet meetings that dealt with the bill (house, meeting, date, official record link); for cabinet bills the cabinet decision date and page. Each block has a status. 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_bill_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoBill title or part of it, in Japanese (used when bill_id is not given)
bill_idNoBill id: submitted session, kind and number, for example 222-閣法-1, 222-cabinet-1, 221-hr-1, 222-hc-2

Output Schema

NameRequiredDescriptionDefault
billYes
queryYes
termsYesURL of the terms of service.
sourceYesWhere the answer comes from and how fresh it is.
statusYes
meetingsNoDiet meetings whose record contains the bill title (meeting-level data and links only; no speeches, no speaker names).
candidatesYes
disclaimerYes
provenanceYesFreshness receipts for every upstream source used.
answered_atYes
attributionYes
status_noteYes
official_checkYes
unknown_reasonYes
cabinet_decisionNoCabinet decision of a cabinet bill from the Prime Minister's Office agenda pages (PDL1.0; keep the source line).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / cabinet_decision
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Cabinet decision of a cabinet bill from the Prime Minister's Office agenda pages (PDL1.0; keep the source line).",
      +  "properties": {
      +    "entries": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "attribution": {
      +            "additionalProperties": {},
      +            "properties": {
      +              "source_ja": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "source_ja"
      +            ],
      +            "type": "object"
      +          },
      +          "date": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "item_title_ja": {
      +            "type": "string"
      +          },
      +          "page_url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "date",
      +          "page_url",
      +          "item_title_ja",
      +          "attribution"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "enum": [
      +        "found",
      +        "not_found",
      +        "not_checked",
      +        "not_applicable",
      +        "not_loaded_yet",
      +        "paused",
      +        "upstream_unavailable"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "entries",
      +    "note"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / meetings
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Diet meetings whose record contains the bill title (meeting-level data and links only; no speeches, no speaker names).",
      +  "properties": {
      +    "meetings": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "date": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "house_ja": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "meeting_ja": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "meeting_url": {
      +            "description": "The meeting's page in the Diet Record Search System.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "relation": {
      +            "enum": [
      +              "stage_on_same_day",
      +              "title_mentioned"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "house_ja",
      +          "meeting_ja",
      +          "date",
      +          "meeting_url",
      +          "relation"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "retrieved_at": {
      +      "description": "When this service's scheduled job read the meeting record API for this bill.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "enum": [
      +        "found",
      +        "not_found",
      +        "not_loaded_yet",
      +        "paused",
      +        "upstream_unavailable"
      +      ],
      +      "type": "string"
      +    },
      +    "truncated": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "retrieved_at",
      +    "truncated",
      +    "meetings",
      +    "note"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and open-world lookup are covered. The description adds genuine context beyond them — provenance (source URL, official record link), freshness ('first observed time'), and a cost signal ('Free') — but it never says what happens when a title is ambiguous or a bill is not found, which matters for an open-world lookup.

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?

The lead question front-loads the purpose, and the enumerated return content is scannable. It is dense — one long sentence carries all the return detail, and 'Each block has a status' plus the trailing 'Free.' are minor filler given an output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, most of the return-value enumeration is redundant, while the actually risky cases are unaddressed: both parameters are optional, so the description should say what a no-argument call does, and title lookup ambiguity is unexplained. Adequate but with clear gaps for a tool of this shape.

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%, so both parameters are already documented with their own format examples, and the description largely restates them. It adds no new semantics such as precedence when both bill_id and title are supplied, or what occurs when neither optional parameter is given.

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 opens with a specific question ('Where is this Diet bill now and how did it get there?') and states the resource is a single bill's status, position and timeline, which is far more precise than the title alone. It does not explicitly contrast itself with plausible siblings like jp_diet_law_history or jp_diet_bills_list, so an agent must infer the boundary rather than read it.

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 two lookup forms ('Give bill_id ... or a title') and by the single-bill scope, which suggests it is the per-bill drill-down rather than a list endpoint. There is no explicit when-to-use, when-not-to-use, or named alternative, so routing between this and the list/history siblings is left to inference.

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