Skip to main content
Glama

SquawkFlow Market Structure

Congressional stock disclosures: three dates per record

get_congressional_disclosures
Read-onlyIdempotent

Use this when the question is what a member of Congress disclosed buying or selling, or who disclosed trading a ticker. Every record carries three separate dates and never collapses them: the transaction date the filing states, the filer notification date where the source states one, and the public disclosure date the filing became available. The lag between the first and the last is published, or null with the reason it could not be computed. Coverage: US House Clerk periodic transaction reports and Senate eFD reports, read from the primary sources rather than from a vendor aggregation. Not for: why a filing was made, whether a trade was well timed, any performance measure, any ranking of filers, or any connection between a filing and a committee. Institutional 13F filings are a different tool (get_filing_receipt). Limits: disclosure is permitted up to roughly 45 days after a transaction, so this is a record of what became public rather than of what is happening. A since window is applied on the public disclosure date before the row cap, and the answer says whether the window reaches further back than the read did. Amounts are the bands the filing uses, never a point estimate. Amendments are appended as new records and an amendment can carry a null lag by design, with the reason published in place of a number. Filings that could not be machine-read are counted and reported on every answer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_congressional_disclosures"
  }
}

Input Schema

NameRequiredDescriptionDefault
filerNoOptional filer name, matched loosely against the name as the filing states it.
limitNoRecords to return, 1 to 100. Newest public disclosure first.
sinceNoISO date. Filters on the PUBLIC DISCLOSURE date, not the transaction date, because disclosure is the date the record became knowable. The endpoint applies the window before its own row cap, so the window is the whole window rather than whatever survived the cap.
symbolNoOptional ticker filter, for example NVDA. Omit for all symbols.
chamberNoHouse or Senate. Omit for both.

Output Schema

NameRequiredDescriptionDefault
kindYes
pageYes
toolYes
notesYes
staleNo
tableNo
titleYes
usageNo
sourceYes
metricsYes
versionYes
capturedAtNo
source_urlNo
staleSinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / page / properties / linkLabel
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / source_url
      Added value: +{
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / usage
      Added value: +{
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedOutput schema / properties / page / properties / url
      Added value: +{
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / since / description
      Previous value: -"ISO date. Filters on the PUBLIC DISCLOSURE date, not the transaction date, because disclosure is the date the record became knowable."New value: +"ISO date. Filters on the PUBLIC DISCLOSURE date, not the transaction date, because disclosure is the date the record became knowable. The endpoint applies the window before its own row cap, so the window is the whole window rather than whatever survived the cap."
  6. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description still adds substantive behavior: three dates are never collapsed, transaction amounts are always filing bands not point estimates, amendments arrive as additional records with a null lag by design, unreadable filings are counted in every answer, and the since window is applied before the row cap. The 45-day permitted disclosure lag is disclosed so the agent understands the record reflects what became public, not live activity.

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?

The description is front-loaded with the use case, then dates, coverage, exclusions, and limits, so the agent hits the decision-relevant material early. It is dense and a few clauses (notably the since-window-before-row-cap statement) duplicate the schema, but almost every sentence carries distinct information for a tool with this much nuance.

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?

An output schema exists, so return values need not be explained, and the description instead covers what makes this dataset tricky: primary-source coverage of House Clerk and Senate eFD, the three-date model, null lags with published reasons, and amendment handling. That is complete for a read-only multi-source lookup with five optional parameters.

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 every parameter is already documented, and the description's point about the since window filtering on public disclosure before the row cap restates what the schema says. It adds no new syntax or format detail for filer, symbol, chamber, or limit. Baseline 3 is the right call when the schema carries the parameter semantics.

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 first sentence names a specific verb and resource — what a member of Congress disclosed buying or selling, or who traded a ticker — which is concrete enough for an agent to route on. It also distinguishes this from institutional 13F filings by naming get_filing_receipt as a different tool.

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

Usage Guidelines5/5

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

It gives an explicit use condition ('Use this when the question is what a member of Congress disclosed buying or selling') and an explicit exclusion list ('Not for: why a filing was made, whether a trade was well timed, any performance measure, any ranking of filers'). The alternative for 13F filings is named, so nothing about tool selection is left to inference.

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.

Resources