Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official
by signal8ai
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get Legislative Calendar

get_legislative_calendar
Read-only

Retrieve upcoming House/Senate floor votes that could impact stock tickers, with predicted vote windows and verified affected companies.

Instructions

Forward-looking legislative catalyst calendar: upcoming House/Senate floor votes (bills and Senate cloture motions) filtered to items that can move tickers. Each item includes the predicted vote window (start/end/granularity/confidence/provenance), marketRelevance (low/medium/high), significance (1-5), affected sectors with direction + mechanism, verified affected tickers with evidence quotes, pass outlook, considerationProcedure (suspension-calendar bills pass ~98% of the time), a conflictBadge when the sponsor traded a verified affected ticker, and tweet/plain summaries. An EMPTY calendar is a normal state — it means nothing market-relevant is scheduled in the window, not an error. Defaults: from=today, to=+14 days, minRelevance=low. IMPORTANT: affectedTickers contains VERIFIED rows only — every ticker carries a verbatim evidenceQuote substring-verified against the actual bill text (no hallucinated tickers). sponsorTradeFacts are restatements of public STOCK Act disclosures with verbatim amount brackets and BOTH transactionDate AND disclosureDate — always cite both dates together (disclosures lag trades by up to 45 days), and never present a fact as evidence of wrongdoing. Vote windows are predictions: check window.provenance for trust level ('uc_explicit' is exact; 'rule_xxii_computed' is a medium-confidence estimate) and window.granularity for how precise the window is (exact time vs day vs week).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLatest vote-window date inclusive (YYYY-MM-DD, default: today + 14 days)
fromNoEarliest vote-window date inclusive (YYYY-MM-DD, default: today)
limitNoMaximum results to return (default: 25, max: 100)
offsetNoPagination offset (default: 0)
minRelevanceNoMinimum market relevance: 'low' (default), 'medium', 'high', or 'none' (explicit opt-in to the full audit trail incl. non-market items — rarely useful)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

The description goes beyond the readOnlyHint annotation by detailing behavioral traits: EMPTY calendar is normal (not an error), affectedTickers are verified, vote windows are predictions with provenance, and sponsor trade facts are restatements not evidence of wrongdoing. This provides comprehensive 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.

Conciseness4/5

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

The description is thorough but efficiently structured, front-loading the main purpose. While slightly lengthy, every sentence adds necessary context for a complex tool, making it justified.

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?

Given the complexity and presence of an output schema, the description covers all essential aspects: return item structure, default parameters, behavior when empty, and data quality notes. It is fully complete for agent understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining the minRelevance enum in detail, especially the 'none' option, and by restating defaults and important notes, enhancing parameter understanding.

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 description clearly states it is a 'Forward-looking legislative catalyst calendar' listing upcoming House/Senate floor votes filtered to items that can move tickers, distinguishing it from sibling calendar tools like get_economic_calendar and get_earnings_calendar.

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

Usage Guidelines4/5

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

The description provides defaults (from=today, to=+14 days, minRelevance=low) and explains that an empty calendar is normal, giving clear context for use. However, it does not explicitly state when to use this tool versus alternatives or when not to use it.

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/signal8ai/signal8-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server