Skip to main content
Glama

parliament_initiative

Full record of one initiative: every phase with dates, every vote with each group's position, text link.

Args: initiative_id: the id from parliament_search (e.g. "356403"), or a reference like "Proposta de Lei 3".

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": {
      "initiative_id": "<initiative_id>"
    },
    "name": "parliament_initiative"
  }
}

Input Schema

NameRequiredDescriptionDefault
legislatureNo
initiative_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the disclosure burden. It usefully characterizes the returned content (full phase history, per-group vote breakdown, text link), implying a read-only detail fetch, but says nothing about authentication, rate limits, or behavior for an invalid/missing initiative id.

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?

The content summary is front-loaded in a single dense clause, then the args block. No filler, though the prose-style 'Args:' block mixed into a description is slightly awkward for an agent parsing intent.

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?

An output schema exists, so the description needn't explain return structure, and it still gives a useful preview of what the record contains. The one incompleteness is the undocumented `legislature` parameter for a tool whose id may need session scoping.

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 there is no description of `legislature` anywhere, which is a real gap since it likely scopes which parliamentary session the id refers to. The `initiative_id` param is well served though: format example ("356403") plus the accepted free-text reference form adds meaning beyond the bare string type.

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?

States a specific resource and enumerates exactly what the record contains (phases with dates, per-group vote positions, text link), which distinguishes it from the search-style siblings. It doesn't explicitly name parliament_search as its complement in the purpose line, only in the args block, so it stops short of a 5.

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

Usage Guidelines4/5

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

The args section explicitly states where the identifier comes from ("the `id` from parliament_search"), giving the agent a concrete entry path and an alternative accepted form ("Proposta de Lei 3"). No when-not-to-use guidance is given, so it isn't a full 5.

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.