Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

congress_stock_disclosures

Search House and Senate congressional stock-disclosure filings. Use filters for chamber, member, state, filing date, and report type to locate public financial disclosures.

Instructions

Search congressional stock-disclosure filings. Search public congressional stock disclosure filings (House or Senate).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoMaximum filing date. House accepts YYYY. Senate accepts YYYY or MM/DD/YYYY.
fromNoMinimum filing date. House accepts YYYY. Senate accepts YYYY or MM/DD/YYYY and defaults to 2012 when omitted.
pageNo1-based result page (1-1000).
sortNoSort key. Allowed values: name_asc, name_desc, office_asc, office_desc, filing_year_asc, filing_year_desc.
limitNoMax results (1-500).
stateNoState or territory filter (2-letter code). For Senate this backward-compatible shorthand applies to both Senator and Candidate states and cannot be combined with senator_state or candidate_state.
memberNoMember name. Required for House. For Senate, this backward-compatible shorthand maps one word to last_name and maps the first word plus the complete remaining surname to first_name/last_name; it cannot be combined with either exact name field.
tickerNoDeprecated unsupported parameter; any non-empty value returns a validation error and the parameter is planned for removal.
chamberNoChamber filter. Allowed values: house, senate.
districtNoHouse district filter (House only).
last_nameNoSenate filer last-name prefix (Senate only; cannot be combined with member).
filer_typeNoFiler-type filter, meaning differs by chamber. House: member (default) or candidate. Senate: comma-separated senator, candidate, former_senator, or the standalone all value. Defaults to senator when omitted.
first_nameNoSenate filer first-name prefix (Senate only; cannot be combined with member).
report_typeNoComma-separated Senate report-type filter (Senate only). Allowed values: annual, periodic_transaction, due_date_extension, blind_trust, other. Defaults to all types when omitted.
election_yearNoHouse candidate-search election year filter (requires filer_type=candidate).
senator_stateNoSenator state filter (Senate only, 2-letter code).
candidate_stateNoCandidate state filter (Senate only, 2-letter code).
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. The word 'search' implies a read operation, and 'public' hints at accessibility, but the description does not disclose important behavior such as the deprecated ticker parameter, chamber-specific defaults, validation errors, or parameter compatibility constraints.

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 short but contains redundancy: the second sentence 'Search public congressional stock disclosure filings (House or Senate)' largely repeats the first sentence with only slight additions ('public' and chamber scope). An ideal description would merge these or front-load the chamber scope more efficiently.

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?

For a tool with 17 parameters, no required fields, no output schema, and complex chamber-specific behavior, the description is far too sparse. It does not give the agent a high-level understanding of how to structure a request or what results to expect, leaving the agent to rely entirely on the schema descriptions.

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 all 17 parameters documented in the input schema. The description adds no additional parameter meaning beyond what the schema already provides, so the 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?

The description clearly states the specific action (Search) and resource (congressional stock-disclosure filings), and explicitly scopes it to House or Senate filings. This makes the tool's purpose unambiguous and distinct from the sibling congress_report tool.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. The only context is the statement that it searches public filings, which is implicit in the tool name.

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/Crawlora-org/crawlora-mcp'

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