Skip to main content
Glama

Politician Member Activity

politician_member_activity
Read-onlyIdempotent

Detail view for a single member of Congress (or executive-branch filer): full lifetime trade count, windowed activity, late-filing rate, avg days-to-file, estimated disclosed volume, and avg excess return vs SPY across disclosed trades, the closest the public data gets to "this member's trades have been beating the index". Accepts a full name ("Nancy Pelosi"), a last name ("Pelosi"), or a canonical filer id ("house_nancy_pelosi").

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "days": 365,
      "member": "Nancy Pelosi"
    },
    "name": "politician_member_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days for windowed stats. Default 365.
memberYesRepresentative name (last name or full) or canonical filer id.

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?

Annotations already declare readOnly, idempotent, open-world semantics, so the safety profile is covered. The description adds substantive behavior: it distinguishes lifetime vs windowed statistics, notes 'estimated disclosed volume' (implying approximation) and frames excess return as 'the closest the public data gets' to index-beating, which honestly signals the metric's limits. It stops short of stating data recency/filing lag or what happens for an unknown member, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, followed by the metric list and then input formats. The long metric enumeration is information-dense rather than padded, though the first sentence is heavy and could be broken up for faster scanning.

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?

With no output schema, the description carries the return-value burden and discharges it by naming every metric returned, plus the accepted identifier forms and the window parameter's effect. Missing only secondary details such as filing lag/freshness and not-found behavior, which matter for a filing-based dataset but are not essential to a correct call.

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 coverage is 100%, so both parameters are already documented, and the description's 'full name, last name, or canonical filer id' largely restates the schema. It does add a concrete canonical-id format example ('house_nancy_pelosi') that clarifies the otherwise underspecified identifier shape, so slightly above baseline but not a rich addition.

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

Purpose5/5

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

Opens with a specific verb+resource ('Detail view for a single member of Congress') and enumerates exactly what the view contains (lifetime trade count, windowed activity, late-filing rate, avg days-to-file, disclosed volume, excess return vs SPY). This makes it plainly distinct from sibling list-style tools like politician_recent_trades and politician_top_movers without needing to open a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: 'detail view for a single member' signals a per-entity profile lookup, and the accepted identifier formats tell the agent how to invoke it. However, there is no explicit statement of when this should be chosen over politician_recent_trades or politician_top_movers, and no exclusions or prerequisites (e.g., requires a US filer) are given.

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.