Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

congress_stock_disclosures

Search congressional stock-disclosure filings for House and Senate members, candidates, and former senators. Filter by chamber, member, state, district, filing year, and report type.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoMaximum filing year (YYYY).
fromNoMinimum filing year (YYYY).
sortNoSort key. Allowed values: name_asc, name_desc, office_asc, office_desc, filing_year_asc, filing_year_desc.
limitNoMax results (1-500).
stateNoMember state filter (2-letter code).
memberNoChamber member name (required when ticker is omitted).
tickerNoTicker symbol filter. Not supported by House or Senate sources.
chamberNoChamber filter. Allowed values: house, senate.
districtNoHouse district filter (House only).
filer_typeNoFiler-type filter, meaning differs by chamber. House: single value selecting between the site's two separate search forms -- member (default, Search Members) or candidate (Search Candidates; results[].filing_year holds election year instead of a filing year). Senate: comma-separated multi-select -- senator, candidate, former_senator. Defaults to senator when omitted.
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).
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Search' and 'public' filings, giving no information about rate limits, authentication, pagination, return format, or other operational behaviors.

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

Conciseness2/5

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

The description is redundant, repeating 'Search...filings' in both sentences with only minor variations ('public', 'House or Senate'). It could be condensed into one concise sentence, so the structure is not efficient.

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?

With 12 optional parameters and no output schema, the description is too thin. It does not explain how parameters interact, expected result structure, or any constraints, leaving an agent with significant ambiguity for such a complex tool.

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?

The input schema provides descriptions for all 12 parameters, giving 100% coverage. The description adds no extra meaning beyond the schema, so the baseline 3 is appropriate.

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 uses a specific verb 'Search' and a specific resource 'congressional stock-disclosure filings', and clarifies it covers House or Senate. However, it does not explicitly distinguish this from the related sibling tool 'congress_report', so it falls just short of a 5.

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, no exclusions, and no prerequisites. It only repeats the search action without contextualizing when this tool is the appropriate choice.

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