Skip to main content
Glama
Parliament MCP (India)

Parliament MCP (India)

by lhasao

list_members

Lists current Indian MPs with filters for house, state, or party, plus pagination. Use it to identify sitting Lok Sabha or Rajya Sabha members when you need accurate, up-to-date parliamentary rosters.

Instructions

List current MPs. Filter by house ("Lok Sabha" or "Rajya Sabha"), state, or party. Paginated (limit 1–200).

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_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
houseNo
limitNo
partyNo
stateNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It discloses pagination bounds (limit 1–200) and that only sitting members are returned ("current MPs"), but says nothing about defaults, the offset mechanism, or what the response contains.

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?

Three short sentences, front-loaded with purpose, then filters, then pagination constraint. No filler words and nothing redundant.

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?

For a five-parameter, unannotated, no-output-schema tool, the definition is adequate but thin: offset semantics and the shape of the returned member records are unaddressed, leaving an agent unsure how to page through results correctly.

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%, so the description must document five parameters. It adds real value by naming the accepted house values ("Lok Sabha"/"Rajya Sabha") since the schema declares no enum, but state and party formats (exact match, casing, spelling) and the offset parameter are left unexplained.

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?

"List current MPs" gives a specific verb and resource, and the filter sentence narrows the scope. It does not explicitly contrast with search_members or get_member, so an agent must infer that this is the browse/enumerate path rather than the lookup path.

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?

The mention of house/state/party filters implies the browse-and-filter use case, but there is no explicit statement of when to prefer this over search_members for keyword queries or get_member for a single MP. Usage is inferable rather than stated.

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