Skip to main content
Glama

House Ptr Late Filers

house_ptr_late_filers
Read-onlyIdempotent

Which House members filed their stock-trade reports late, ranked across the WHOLE House for a filing-date window: per member the number of transactions, how many were filed more than 45 days after the trade (the STOCK Act limit), late share, average and worst days-to-file. Use for "which members filed late this quarter", "worst late filers in the House this year". House only; computed from the Clerk of the House's own filings, with a coverage block stating how many filings could not be read.

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": {
      "to": "2025-12-31",
      "from": "2025-01-01",
      "limit": 5
    },
    "name": "house_ptr_late_filers"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLatest FILING date, YYYY-MM-DD. Default: today.
fromNoEarliest FILING date, YYYY-MM-DD. Default: 90 days ago.
limitNoMax members, default 25, max 100.
min_transactionsNoOnly members with at least this many transactions in the window. Default 3.

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
sourceNo
membersNo
coverageNo
late_ruleNo
data_as_ofNo
filing_date_windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the ranking is computed from the Clerk of the House's own filings, late is defined against the 45-day STOCK Act limit, and a coverage block reports unreadable filings — an honest disclosure of data-quality limits. No return-shape detail is needed since an output schema exists.

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?

Front-loads what is ranked and the scope, then gives the metric list, then usage examples and the House-only caveat. Dense but every clause carries information; the single long opening sentence is the only mild readability cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-param, fully documented, output-schema-backed read tool, the description supplies the remaining judgment-critical facts: the ranking universe (whole House), the 45-day statutory definition, the source of truth (Clerk filings), and the coverage caveat. An agent can call this correctly and interpret the results without further guidance.

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%, so all four parameters (from, to, limit, min_transactions) are already documented with defaults and bounds. The description adds only the framing that the window is a FILING-date window and the 45-day threshold used for the late calculation; it does not extend per-parameter meaning beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource — ranks House members by late stock-trade filings across the WHOLE House for a filing-date window — and enumerates the exact metrics returned (transaction count, late count, late share, average/worst days-to-file). This clearly distinguishes it from house_ptr_search and politician_recent_trades, which are member/lookup-oriented rather than cross-House rankings.

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

Usage Guidelines4/5

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

Provides concrete trigger phrasings ("which members filed late this quarter", "worst late filers in the House this year") and states the scope constraint "House only." It does not explicitly name a sibling alternative or an exclusion (e.g., use house_ptr_search for a single member's filings), which keeps it from a 5.

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.