Skip to main content
Glama
Parliament MCP (India)

Parliament MCP (India)

by lhasao

list_bills

Retrieve currently tracked parliamentary bills and their examining committees to verify India's legislative status instead of guessing from memory.

Instructions

Bills currently tracked, with the committees examining them.

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": "list_bills"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the meaningful scope constraint ("currently tracked," i.e., active bills only) and the join with examining committees, which is behavior beyond a bare list. However, it says nothing about result size, pagination, ordering, or whether the whole set is returned at once, and a read-only nature is only implied by "list".

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?

A single short sentence, front-loaded with the resource and followed by the returned association; nothing is redundant. It is arguably too terse rather than bloated, so the score reflects efficiency rather than optimal informativeness.

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?

An output schema exists, so return-value explanation is not required, and with zero parameters there is little schema surface to cover. Still, with no annotations at all, the description leaves an agent without any routing guidance or sense of result volume/pagination for what is likely a large collection.

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 zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies an unfiltered enumeration consistent with an empty argument object.

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?

"Bills currently tracked, with the committees examining them" names the specific resource (bills), the scope of the set (currently tracked), and the association returned (examining committees), so an agent can distinguish it from list_committees and list_members by resource alone. It stops short of explicitly contrasting itself with any sibling such as relevant_mps_for_bill.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of an alternative (e.g., a per-bill lookup or search tool) that an agent might pick instead. The only implicit cue is "currently tracked," which suggests a broad enumeration rather than a filtered lookup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.