Skip to main content
Glama

Japan Diet: parliamentary group votes of a session

jp_diet_group_votes
Read-only

How did each parliamentary group (会派) vote on the law bills of a Diet session? From the House of Representatives bill progress pages: for each bill with a plenary vote, the groups for and against as published (names exactly as published, not merged across renames), a bills x groups table, and pairwise agreement between groups (share of bills where both were on the same side, with n). Group-level public votes only; no individual members. 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_group_votes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNoDiet session number, for example 222 (default: the current session)

Output Schema

NameRequiredDescriptionDefault
noteYes
billsYes
queryYes
termsYesURL of the terms of service.
groupsYes
sourceYes
statusYes
agreementYes
disclaimerYes
provenanceYesFreshness receipts for every upstream source used.
answered_atYes
attributionYes
official_checkYes
unknown_reasonYes
observation_noteYes
session_coverageYes
bills_without_group_dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing provenance (House of Representatives bill progress pages), a data-handling quirk an agent would otherwise misread ('names exactly as published, not merged across renames'), the exact definition of the agreement metric ('share of bills where both were on the same side, with n'), coverage limits (only bills with a plenary vote), and cost ('Free'). That is precisely the behavioral context structured fields cannot carry.

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 core question is front-loaded and every following clause adds a distinct fact (source, output shape, name handling, metric definition, scope limit, cost). The long colon-introduced list in the middle sentence makes it dense and slightly hard to scan, but there is no filler.

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

Completeness5/5

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

For a single-parameter, read-only tool with an output schema, this is more than complete: it explains the data source, the record granularity, the shape of each returned component, and the caveat about unmerged group names. Nothing an agent needs in order to call it correctly or interpret the results is missing.

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?

With a single parameter at 100% schema description coverage, the schema already documents the session number, its 1-999 range and the current-session default. The description only echoes 'of a Diet session' without adding format, fallback behavior for missing sessions, or what happens when a session had no plenary votes.

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?

The opening question states a specific verb (voted), resource (law bills of a Diet session) and unit (parliamentary group / 会派), then enumerates the three concrete outputs: for/against lists, a bills x groups table, and pairwise agreement. It also explicitly carves out member-level data ('Group-level public votes only; no individual members'), which separates it from sibling tools like 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear context for use — comparing how groups voted within one session, with the source named as House of Representatives bill progress pages — and an explicit scope exclusion (no individual members). What it lacks is any routing language naming an alternative tool for the cases it does not cover (e.g. per-bill status or per-member data), leaving the agent to infer that from sibling names 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