Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

congress_stock_disclosures

Search public congressional stock-disclosure filings for House or Senate members by name, state, date, and report type to track financial trades.

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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.17.5
    • addedInput schema / properties / candidate_state / enum
      Added value: +[
+  "AK",
+  "AL",
+  "AR",
+  "AS",
+  "AZ",
+  "CA",
+  "CO",
+  "CT",
+  "DC",
+  "DE",
+  "FL",
+  "FM",
+  "GA",
+  "GU",
+  "HI",
+  "IA",
+  "ID",
+  "IL",
+  "IN",
+  "KS",
+  "KY",
+  "LA",
+  "MA",
+  "MD",
+  "ME",
+  "MH",
+  "MI",
+  "MN",
+  "MO",
+  "MP",
+  "MS",
+  "MT",
+  "NC",
+  "ND",
+  "NE",
+  "NH",
+  "NJ",
+  "NM",
+  "NV",
+  "NY",
+  "OH",
+  "OK",
+  "OR",
+  "PA",
+  "PR",
+  "PW",
+  "RI",
+  "SC",
+  "SD",
+  "TN",
+  "TX",
+  "UT",
+  "VA",
+  "VI",
+  "VT",
+  "WA",
+  "WI",
+  "WV",
+  "WY"
+]
    • addedInput schema / properties / chamber / enum
      Added value: +[
+  "house",
+  "senate"
+]
    • addedInput schema / properties / filer_type / enum
      Added value: +[
+  "member",
+  "candidate",
+  "all",
+  "senator",
+  "former_senator"
+]
    • addedInput schema / properties / report_type / enum
      Added value: +[
+  "annual",
+  "periodic_transaction",
+  "due_date_extension",
+  "blind_trust",
+  "other"
+]
    • addedInput schema / properties / senator_state / enum
      Added value: +[
+  "AK",
+  "AL",
+  "AR",
+  "AS",
+  "AZ",
+  "CA",
+  "CO",
+  "CT",
+  "DC",
+  "DE",
+  "FL",
+  "FM",
+  "GA",
+  "GU",
+  "HI",
+  "IA",
+  "ID",
+  "IL",
+  "IN",
+  "KS",
+  "KY",
+  "LA",
+  "MA",
+  "MD",
+  "ME",
+  "MH",
+  "MI",
+  "MN",
+  "MO",
+  "MP",
+  "MS",
+  "MT",
+  "NC",
+  "ND",
+  "NE",
+  "NH",
+  "NJ",
+  "NM",
+  "NV",
+  "NY",
+  "OH",
+  "OK",
+  "OR",
+  "PA",
+  "PR",
+  "PW",
+  "RI",
+  "SC",
+  "SD",
+  "TN",
+  "TX",
+  "UT",
+  "VA",
+  "VI",
+  "VT",
+  "WA",
+  "WI",
+  "WV",
+  "WY"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "name_asc",
+  "name_desc",
+  "office_asc",
+  "office_desc",
+  "filing_year_asc",
+  "filing_year_desc"
+]
    • addedInput schema / properties / state / enum
      Added value: +[
+  "AK",
+  "AL",
+  "AR",
+  "AS",
+  "AZ",
+  "CA",
+  "CO",
+  "CT",
+  "DC",
+  "DE",
+  "FL",
+  "FM",
+  "GA",
+  "GU",
+  "HI",
+  "IA",
+  "ID",
+  "IL",
+  "IN",
+  "KS",
+  "KY",
+  "LA",
+  "MA",
+  "MD",
+  "ME",
+  "MH",
+  "MI",
+  "MN",
+  "MO",
+  "MP",
+  "MS",
+  "MT",
+  "NC",
+  "ND",
+  "NE",
+  "NH",
+  "NJ",
+  "NM",
+  "NV",
+  "NY",
+  "OH",
+  "OK",
+  "OR",
+  "PA",
+  "PR",
+  "PW",
+  "RI",
+  "SC",
+  "SD",
+  "TN",
+  "TX",
+  "UT",
+  "VA",
+  "VI",
+  "VT",
+  "WA",
+  "WI",
+  "WV",
+  "WY"
+]
  2. Changed11 schema fields changedv1.14.0
    • addedInput schema / properties / candidate_state
      Added value: +{
+  "description": "Candidate state filter (Senate only, 2-letter code).",
+  "type": "string"
+}
    • changedInput schema / properties / filer_type / description
      Previous value: -"Filer-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."New value: +"Filer-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."
    • addedInput schema / properties / first_name
      Added value: +{
+  "description": "Senate filer first-name prefix (Senate only; cannot be combined with member).",
+  "type": "string"
+}
    • changedInput schema / properties / from / description
      Previous value: -"Minimum filing year (YYYY)."New value: +"Minimum filing date. House accepts YYYY. Senate accepts YYYY or MM/DD/YYYY and defaults to 2012 when omitted."
    • addedInput schema / properties / last_name
      Added value: +{
+  "description": "Senate filer last-name prefix (Senate only; cannot be combined with member).",
+  "type": "string"
+}
    • changedInput schema / properties / member / description
      Previous value: -"Chamber member name (required when ticker is omitted)."New value: +"Member 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."
    • addedInput schema / properties / page
      Added value: +{
+  "description": "1-based result page (1-1000).",
+  "type": "integer"
+}
    • addedInput schema / properties / senator_state
      Added value: +{
+  "description": "Senator state filter (Senate only, 2-letter code).",
+  "type": "string"
+}
    • changedInput schema / properties / state / description
      Previous value: -"Member state filter (2-letter code)."New value: +"State 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."
    • changedInput schema / properties / ticker / description
      Previous value: -"Ticker symbol filter. Not supported by House or Senate sources."New value: +"Deprecated unsupported parameter; any non-empty value returns a validation error and the parameter is planned for removal."
    • changedInput schema / properties / to / description
      Previous value: -"Maximum filing year (YYYY)."New value: +"Maximum filing date. House accepts YYYY. Senate accepts YYYY or MM/DD/YYYY."
  3. Added

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention any constraints like read-only nature, pagination limits, default sorting, or what kind of data is returned. The phrase 'public' implies accessibility, but no explicit behavioral traits are revealed beyond the basic search action.

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 consists of two sentences that essentially repeat the same information: 'Search congressional stock-disclosure filings' and 'Search public congressional stock disclosure filings (House or Senate).' This is redundant and wastes a sentence without adding meaningful detail. It is not front-loaded with unique insights; both sentences convey nearly identical content.

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 tool's complexity (17 parameters, no output schema, no annotations), the description is notably sparse. It does not explain what the search returns, how to combine parameters, what defaults apply, or any high-level behavior. The schema covers parameter semantics, but the description fails to provide an overview that would help an agent understand the tool's scope and expected results.

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 the schema already documents all 17 parameters, including types, constraints, and chamber-specific behavior. The description adds no additional information about parameters or their usage. According to the rubric, with high schema coverage, a baseline of 3 is appropriate, and the description provides no extra value beyond the schema.

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 clearly states the tool's function: searching congressional stock-disclosure filings, specifying the domain and the generic action (search). It distinguishes itself from the vast sibling list by focusing on a unique resource (congressional stock filings), though it doesn't explicitly name alternatives. The repetition of 'Search public congressional stock disclosure filings (House or Senate)' reinforces the purpose but adds little new information.

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 prerequisites, and no conditions for invocation. It simply states what it does without any context about typical use cases, required filters, or when another tool might be more appropriate. The agent is left entirely without direction.

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

Deploy Server

Other Tools