mcp-camara-pecs
Related Servers
Alternatives to mcp-camara-pecs
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceEnables searching and retrieving Brazilian legislative propositions, reading their full texts, finding related propositions, and accessing dataset releases and downloads with provenance and official source URLs.7MIT- AlicenseBqualityNot gradedmaintenanceEnables interaction with the Brazilian Chamber of Deputies Open Data API, providing access to information about legislators, legislative proposals, voting records, events, committees, and parliamentary activities through 57 typed and validated tools.63-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query Brazilian Senate data including senators, bills, voting records, committees, and plenary sessions through natural language.9 npm6MIT
- AlicenseAqualityAmaintenanceMCP server for the Brazilian Chamber of Deputies open-data API, enabling search and retrieval of federal legislative bills and their status.1542 PyPI1Apache 2.0
- FlicenseAqualityDmaintenanceEnables querying Brazilian electoral data through TSE's official API. Supports candidate searches, election information, and campaign finance records for municipalities and states.72-
- AlicenseNot gradedqualityCmaintenanceEnables querying UK Parliament data including MPs, Lords, bills, Hansard debates, and divisions.2 npmMIT
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action (list/detail PECs, authors, history, votes, orientations). There is no ambiguity or overlap between tools, and the descriptions clearly tie each tool to its unique role.
All names use a snake_case verb_noun pattern with the verbs listar/detalhar, which is highly predictable. The only minor inconsistency is pluralization (listar_pecs vs listar_autores_pec), but this does not confuse the overall convention.
8 tools is well-scoped for a PEC-focused legislative server: enough to cover discovery, detail, authors, history, and voting workflows without unnecessary bloat. Each tool earns a clear place.
The tool surface provides a complete read-only lifecycle for PECs: list and search, full detail, authors, procediment history, voting events, individual votes, and party orientations. No obvious gaps prevent an agent from answering typical PEC-related queries.