Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

congress_report

Fetch and parse a Senate congressional disclosure report from a filing URL, returning structured data for stock and financial disclosures.

Instructions

Fetch and parse a congressional disclosure report. Fetch a single disclosure report by its filing_url (as returned by.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFiling URL, as returned by congress-stock-disclosures' filing_url field. Must be an efdsearch.senate.gov /search/view/annual/..., /search/view/ptr/..., or /search/view/extension-notice/regular/... URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. 'Fetch and parse' indicates a read operation, but there is no mention of side effects, authentication, rate limits, or what parsing entails. The truncated description offers minimal behavioral context.

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 brief but incomplete—the second sentence cuts off mid-phrase ('as returned by.'). This is not well-structured conciseness; it is under-specification that hinders understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool, the schema covers the parameter thoroughly, and the operation is simple. However, the description does not explain the return value, parsing behavior, or URL requirements (left to the schema), and the truncation creates a gap. This is minimally adequate.

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 coverage is 100% with a detailed description of the 'url' parameter. The tool description itself adds no additional parameter semantics beyond the schema, so the baseline of 3 applies.

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 first sentence clearly states the tool fetches and parses a congressional disclosure report. However, the description is truncated mid-sentence ('as returned by.'), which reduces clarity and fails to explicitly differentiate it from sibling tools like congress_stock_disclosures.

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

Usage Guidelines3/5

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

The description hints at usage context ('by its filing_url'), implying it should be used with URLs from congress-stock-disclosures, but the sentence is incomplete. It does not state when to use this tool versus alternatives or provide exclusions.

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