Skip to main content
Glama

parliament_search

Search initiatives in the Portuguese Parliament: bills, resolutions, inquiries.

Args: query: words in the title, e.g. "habitação", "IRS", "imigração". type: e.g. "Projeto de Lei", "Proposta de Lei" (Government bills), "Projeto de Resolução". author: party acronym ("PS", "PSD", "CH", "IL", "L", "PCP", "BE", "CDS-PP", "PAN", "JPP") or "Governo". result: "aprovado" or "rejeitado" — keeps initiatives whose latest vote had this result. since: "YYYY-MM-DD" — submitted on or after this date. legislature: Roman numeral, default the current one (XVII). limit: max results, newest first.

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

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
queryNo
sinceNo
authorNo
resultNo
legislatureNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does add useful context: it specifies that results are newest-first, that legislature defaults to the current one, and that 'result' filters on the latest vote outcome. It does not discuss pagination or error behavior, but for a read-only search tool this is largely sufficient.

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?

The purpose is front-loaded in a single clear sentence, followed by a compact parameter list with no filler. Every argument line delivers actionable detail without repetition.

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 return values need not be explained. For a 7-parameter search tool the description covers all parameters and key behaviors; it lacks only minor details such as whether filters are combined with AND logic or whether results beyond limit can be paginated.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does so thoroughly: it gives examples for query terms, valid type strings, party acronyms, result values ('aprovado'/'rejeitado'), date format for since, the Roman-numeral default for legislature, and the meaning of limit. Every parameter gains concrete meaning beyond the bare schema.

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 verb and resource ('Search initiatives in the Portuguese Parliament') and clarifies the scope with examples of initiative types (bills, resolutions, inquiries). It does not explicitly contrast with sibling tools like parliament_initiative or parliament_votes, so sibling differentiation is left implicit.

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?

The description explains what the tool does and how to fill in parameters, but never states when to use it versus alternatives such as parliament_initiative (for a single initiative) or parliament_votes. No exclusions or prerequisites are given, leaving the agent to infer usage context entirely.

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.