Recently DISCLOSED stock trades by members of the US Congress, newest transaction first. Source: House and Senate periodic transaction reports, which may be filed up to 45 days after the trade — the newest disclosure is not the newest trade. Members disclose dollar amounts as ranges, never exact figures.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, the description discloses important behavioral traits: the data comes from periodic reports, the newest disclosure is not the newest trade, and dollar amounts are only given as ranges. These caveats inform users about data limitations and reliability, adding significant value.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three concise sentences that front-load the primary purpose, then add essential source context and caveats. Every sentence contributes necessary information without redundancy or fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no parameters and no output schema, the description provides comprehensive context: the exact data source, the 45-day filing delay, the range-based dollar amounts, and the sorting order. It fully covers what a user needs to know to correctly interpret results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and the schema coverage is 100% (empty schema). The description does not need to explain parameters, so the baseline of 4 is appropriate. The description adds no parameter details but none are needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists recently disclosed stock trades by US Congress members, sorted newest first. It uses a specific verb and resource, and the name 'congress_trades' directly matches the function, distinguishing it from sibling tools focused on other financial metrics.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context about the data source and a critical caveat about the 45-day filing delay, helping the user understand when the data is most relevant. It does not explicitly mention alternative tools or when not to use this tool, but the context is sufficient for the tool's straightforward purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct data source or analytical angle: buybacks, congress trades, DCA fit, insider buying, 13F filings, price levels, risk phrases, and options volume. There is no overlap in purpose or output, so an agent can unambiguously select the right tool.
All tool names follow a consistent lowercase_with_underscore noun-phrase pattern (e.g., buyback_leaders, risk_filings). The naming is uniform and descriptive, making it easy to predict what each tool does based on the name alone.
The server has 8 tools, squarely in the well-scoped range. Each tool represents a meaningful, non-redundant screen or data source, and none feels like filler or duplicative functionality.
For a market-aware server, the coverage is strong: it spans corporate actions (buybacks), insider activity, institutional holdings, technical levels, risk signals, and options flow. Minor gaps exist—no general price/quote tool or earnings-focused screen—but the set is coherent and covers diverse data sources without major dead ends.