Skip to main content
Glama
psalzman

MCP OpenFEC Server

by psalzman

get_committee

Retrieve detailed Federal Election Commission committee information, including campaign finance data, by providing a specific FEC committee ID.

Instructions

Get detailed information about a committee

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
committee_idYesFEC committee ID

Implementation Reference

  • The handler function for the 'get_committee' tool. It validates the input committee_id using Zod, consumes a rate limit token, fetches committee details from the OpenFEC API endpoint `/committee/${committee_id}`, and returns the response data as formatted JSON text.
    private async handleGetCommittee(args: any) {
      const schema = z.object({
        committee_id: z.string(),
      });
    
      const { committee_id } = schema.parse(args);
      this.rateLimiter.consumeToken();
    
      const response = await this.axiosInstance.get(`/committee/${committee_id}`);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • src/server.ts:156-169 (registration)
    Registration of the 'get_committee' tool in the ListTools response, including name, description, and input schema definition.
    {
      name: 'get_committee',
      description: 'Get detailed information about a committee',
      inputSchema: {
        type: 'object',
        properties: {
          committee_id: {
            type: 'string',
            description: 'FEC committee ID',
          },
        },
        required: ['committee_id'],
      },
    },
  • src/server.ts:451-452 (registration)
    Dispatcher switch case in CallToolRequestSchema handler that routes 'get_committee' calls to the handleGetCommittee method.
    case 'get_committee':
      return await this.handleGetCommittee(request.params.arguments);
  • Runtime input validation schema using Zod that matches the tool's inputSchema, requiring a committee_id string.
    const schema = z.object({
      committee_id: z.string(),
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get' implies a read-only operation, it doesn't specify authentication requirements, rate limits, error conditions, or what format the 'detailed information' returns. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 description is a single, efficient sentence with no wasted words. It's appropriately sized for a simple lookup tool and gets straight to the point without unnecessary elaboration.

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 the lack of annotations and output schema, the description is insufficiently complete. It doesn't explain what 'detailed information' includes, how results are structured, or any behavioral constraints. For a tool that presumably returns structured data about committees, more context about the response format would be helpful.

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 description coverage is 100%, with the single parameter 'committee_id' clearly documented as 'FEC committee ID' in the schema. The description adds no additional parameter information beyond what the schema provides, which is acceptable given the high schema coverage but doesn't enhance understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get detailed information about a committee' clearly states the action (get) and resource (committee), making the purpose understandable. However, it's somewhat vague about what 'detailed information' entails and doesn't differentiate this tool from siblings like get_candidate or get_filings that also retrieve information about political entities.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, appropriate contexts, or how it differs from sibling tools like get_candidate (which retrieves candidate data) or get_filings (which retrieves filing data). The agent must infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/psalzman/mcp-openfec'

If you have feedback or need assistance with the MCP directory API, please join our Discord server