Skip to main content
Glama

Japan Diet: sessions and coverage

jp_diet_sessions_list
Read-only

Which Diet sessions does this service hold bill records for? Returns every session the House of Representatives bill pages list (from 142, 1998), newest first: number, type (常会 ordinary, 臨時会 extraordinary, 特別会 special), start and end dates, number of law bills, and how far it is loaded (coverage complete, partial or not_loaded; past sessions are loaded newest first). 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_sessions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
termsYesURL of the terms of service.
countsYes
sourceYesWhere the answer comes from and how fresh it is.
statusYes
coverageYespartial while past sessions are still being loaded.
sessionsYes
disclaimerYes
provenanceYesFreshness receipts for every upstream source used.
answered_atYes
attributionYes
status_noteYes
sessions_noteYes
official_checkYes
unknown_reasonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior. The description adds real context: source (House of Representatives bill pages), starting session 142 (1998), newest-first ordering, the three coverage states, and the incremental loading rule ('past sessions are loaded newest first'), plus 'Free'.

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

Conciseness5/5

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

It is two compact sentences with the scoping question front-loaded and no filler. The field list is slightly redundant with the output schema but stays dense and earns its space.

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?

With an output schema present, return values are already structured. The description supplies the non-obvious parts – coverage semantics, ordering, and the load policy – so an agent has everything it needs for this zero-parameter read.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate. Baseline 4 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?

It states a specific verb and resource – returns every Diet session the House of Representatives bill pages list – and the opening question frames the exact scope. An agent can distinguish it from jp_diet_bills_list, which returns bills rather than sessions.

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?

Use is only implied: 'which sessions does this service hold bill records for' suggests calling it to discover available sessions before querying bills. There is no explicit when-to-use, no named alternative, and no note on when not to call it.

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