Flexreport Finance

list_earnings_announcements

Read-only

List scheduled earnings announcements within a date window, Flexreport names only.

Omit both dates for "who reports today". Results are restricted to Flexreport's
covered universe, so symbols outside coverage are dropped silently.

The optional filters are AND-ed together. `sector`, `industry`, and `market_cap` are
validated against fixed enums server-side; invalid values return a 422, so source them
from the tools named in their descriptions rather than guessing.

Returns `announcements` (empty list when nothing matches); values are strings and
"nan" means not available yet.

Requires auth (your MCP client attaches the OAuth bearer automatically).

Input Schema

TableJSON Schema

Name	Required	Description
`sector`	No	Sector values from list_options("sectors").
`symbols`	No	Limit to these tickers, e.g. ["AAPL","MSFT"].
`end_date`	No	Window end, YYYY-MM-DD; defaults to today. Other formats return 422.
`industry`	No	Industry values from list_sub_industries([...]).
`market_cap`	No	Market-cap buckets: "Small-cap", "Medium-cap", "Large-cap", "Mega-cap".
`start_date`	No	Window start, YYYY-MM-DD; defaults to today. Other formats return 422.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`announcements`	Yes	Scheduled reports in the window; empty when nothing matches.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond readOnlyHint by disclosing silent dropping of out-of-coverage symbols, server-side enum validation returning 422, the AND-combination of filters, empty-list-on-no-match, and that "nan" means not available. This is rich behavioral context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Front-loads the core action, then layers date-window defaults, coverage caveats, and validation notes in short, scannable sentences. Every sentence carries distinct information.

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?

For a 6-param read tool with an output schema, the description covers the missing pieces: date defaults, silent filtering, enum validation, auth, and the "nan" convention. Nothing needed to call it correctly is absent.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: dates default to today, filters combine with AND, and invalid enum values trigger 422. That goes beyond what the schema properties state individually.

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?

States a specific verb (List), resource (scheduled earnings announcements), and scope (within a date window, Flexreport names only). An agent can immediately distinguish this from predict_earnings_move or get_company_event_web.

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?

Gives concrete when-to-use guidance ('Omit both dates for "who reports today"') and warns the filters are AND-ed. It also routes the agent to list_options/list_sub_industries for valid enum values. It stops short of naming an alternative tool for overlapping needs, but the context is clear.

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

All Flexreport Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?