mcp-camara
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_endpointsA | Lists available endpoints for the Brazilian Chamber of Deputies API. This is the primary discovery tool to understand the API's capabilities.
It returns a list of all available operations, including the Use the Returns:
APIResponse: An APIResponse object containing a list of |
| get_endpoint_schemaA | Retrieves the detailed schema for a single API endpoint. Use this tool to understand exactly how to call a specific endpoint, including its required and optional parameters. The Args: path (str): The endpoint path (e.g., '/deputados/{id}'). method (str): The endpoint method (e.g., 'GET'). Returns: APIResponse: An APIResponse object containing the Endpoint schema on success, or an error message. |
| call_endpointA | Calls a specific endpoint of the Brazilian Chamber of Deputies API. This is the final tool in the workflow, used to retrieve the actual data.
The The Args: path (str): The endpoint path (e.g., '/deputados/{id}'). method (str): The HTTP method (e.g., 'GET'). params (dict[str, Any]): A dictionary of parameters for the endpoint. Returns: APIResponse: An APIResponse object containing the requested data on success, or an error message. |
| get_deputy_by_nameB | Retrieves a list of deputies by name. This is a helper tool that abstracts the process of querying for a deputy by name. Args: name (str): The name of the deputy to search for. Returns: APIResponse: An APIResponse object containing a list of deputies on success, or an error message. |
| get_deputy_expensesA | Gets the expenses for a single deputy, specified by name or ID. This tool finds a deputy by their name or ID.
You must provide either Args: name (str | None): The full or partial name of the deputy. id (int | None): The unique ID of the deputy. year (int | None): The year to filter expenses by. month (int | None): The month to filter expenses by. Returns: APIResponse: An APIResponse object containing the deputy's expense data on success, or an error message. |
| get_bills_by_deputyB | Retrieves a list of bills (proposições) by a specific author. This is a helper tool that abstracts the process of querying bills for a deputy. Args: deputy_id (int): The ID of the deputy authoring the bill. years (list[str] | None): One or more years for when bills were presented. If set to None, the current year is used. Defaults to None. Returns: APIResponse: An APIResponse object containing a list of bills on success, or an error message. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are well-separated into discovery (list_endpoints, get_endpoint_schema), execution (call_endpoint), and helper functions (get_deputy_by_name, get_deputy_expenses, get_bills_by_deputy) that target different resources and operations.
The naming follows a consistent verb_noun pattern throughout (call_endpoint, get_bills_by_deputy, get_deputy_by_name, get_deputy_expenses, get_endpoint_schema, list_endpoints). The only minor deviation is 'list_endpoints' using 'list' instead of 'get' like the others, but this is appropriate for a listing operation.
With 6 tools, this is well-scoped for the server's purpose of interacting with the Brazilian Chamber of Deputies API. It provides a balanced set covering discovery, schema inspection, direct API calls, and common helper operations without being overwhelming.
The tool surface is complete for the domain. It provides full discovery capabilities (list_endpoints, get_endpoint_schema), execution (call_endpoint), and covers key workflows like finding deputies, retrieving their expenses, and getting their bills. There are no obvious gaps that would hinder agent operations.