Skip to main content
Glama
Parliament MCP (India)

Parliament MCP (India)

by lhasao

get_committee

Retrieve a parliamentary committee's chair and full membership by committee ID to verify who sits on it and who leads it in India's legislature.

Instructions

A committee's chair and full membership.

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": {
      "committee_id": "<committee_id>"
    },
    "name": "get_committee"
  }
}

Input Schema

NameRequiredDescriptionDefault
committee_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it does little: it implies a read-only lookup but never confirms it, and says nothing about behavior when committee_id is unknown or malformed, permissions, or result shape beyond two named fields. The only real disclosure is that the response includes the chair and membership.

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

Conciseness3/5

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

It is extremely short and front-loaded, but that brevity comes from under-specification rather than economy — six words that omit the verb, the parameter, and any usage signal. Nothing is wasted, but too little is present.

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

Completeness2/5

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

For a single-parameter lookup with no output schema and no annotations, the description should at minimum state the operation, the identifier semantics, and the returned structure. It names two returned fields but not their format (e.g., whether membership is a list of member ids or names), so an agent cannot confidently predict the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter committee_id is documented nowhere in the description or schema. The description never explains what identifier format is expected (numeric id, bioguide-style code, name) or how to obtain one, leaving the agent to guess.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment "A committee's chair and full membership" does identify the resource and the returned content, which helps separate it from list_committees and get_member. However, it contains no verb and reads as a noun phrase, so the actual operation (fetch/retrieve a single committee by id) is only implied. Purpose is inferable but not stated.

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 distinction from siblings such as list_committees (plural enumerations of committees) or get_member, and no prerequisites. The only hint is the singular 'committee' noun, which an agent must interpret on its own.

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