Skip to main content
Glama
Sign In
statefinance-mcp

statefinance-mcp

by cstillick
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_committee

Retrieve a campaign committee's contribution and expenditure totals by providing its unique committee ID.

Instructions

A committee plus its contribution and expenditure totals.

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 observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, error handling (e.g., missing committee_id), rate limits, or idempotency. The phrase 'plus its contribution and expenditure totals' hints at the return structure but is insufficient.

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?

The description is very short (one sentence), which is concise, but it sacrifices necessary detail. It is not structured with sections or examples, making it too terse for adequate understanding.

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?

Given no output schema and no behavioral annotations, the description should provide more context about the response structure, possible values, or error conditions. It does not, leaving the agent with significant ambiguity.

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

Parameters1/5

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

The input schema has one parameter 'committee_id' with 0% schema description coverage. The description adds no information about this parameter—no explanation of format, examples, or how to obtain it. This is a critical gap for a required parameter.

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?

The description clarifies that the tool returns not just a committee but also its contribution and expenditure totals, which distinguishes it from sibling tools like 'get_candidate' or search tools. However, it lacks an active verb like 'retrieve' and could be more explicit.

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?

No guidance is provided on when to use this tool versus alternatives like 'search_contributions' or 'summary'. The description does not specify context or prerequisites.

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

Deploy Server

Other Tools