Skip to main content
Glama
Parliament MCP (India)

Parliament MCP (India)

by lhasao

relevant_mps_for_bill

Identify the MPs on the committee examining a bill using a PRS bill slug or part of its title.

Instructions

The MPs on the committee examining a bill. Accepts a PRS bill slug or part of the bill's title.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bill": "<bill>"
    },
    "name": "relevant_mps_for_bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
billYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden, and it does disclose the accepted input formats, which is the main behavioral fact an agent needs. It is silent on the obvious risk of a partial-title match hitting multiple bills, and on whether committee membership is filtered by role or session - gaps for a tool with zero annotation coverage.

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?

Two sentences, the return value first and the input contract second, with no filler. Nothing could be removed without losing information.

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 one-parameter, no-output-schema tool, the description covers what it returns and what input it takes, which is close to sufficient. Only ambiguity resolution and error behavior on an unmatched title are left unstated.

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 coverage is 0% and the single parameter is bare ('bill'), so the description must compensate. It does so well by stating both accepted forms (PRS slug or partial title). However, it does not specify matching behavior, normalization, or what happens when the partial title is ambiguous.

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?

Names a specific resource (MPs on the committee examining a bill) and a specific lookup key, which is enough to separate it from siblings like get_committee or list_members. It never states the retrieval verb explicitly, but the noun phrase is unambiguous about what comes back.

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 only implied: the second sentence tells the agent what input to supply, from which one infers 'call this when you have a bill and need its committee MPs.' No when-not-to-use condition and no mention of how it relates to get_committee or list_members.

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