OptimistFi

get_press_releases

Read-only

Company press releases — the EX-99 exhibits attached to 8-K filings.

An 8-K is a cover sheet stating that a release is "furnished as Exhibit 99.1"; the release
itself is the exhibit. Set with_text to pull the release body and its own headline, bounded by
max_chars. Free, straight from EDGAR, and it is the filer's own wording rather than a
newswire's summary of it.
period: a HISTORICAL fiscal year ("2023") — return that year's earnings releases instead of the
latest. This is where ADJUSTED / non-GAAP figures (Adjusted EBITDA, adjusted EPS) and full-year
GUIDANCE from an older quarter live; they are not in the 10-K/10-Q XBRL. with_text=true reads the
body.
Note this is what the issuer PUBLISHED, not press coverage of it — for the filed-event view
(which 8-K item, how significant) use get_filings(kind="events").

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`entity`	Yes
`period`	No
`max_chars`	No
`with_text`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already mark readOnlyHint=true, and the description adds meaningful context: the data is free, sourced from EDGAR, uses the filer's own wording, and represents what the issuer published rather than press coverage. It also clarifies that period can surface non-GAAP figures not present in XBRL, adding useful behavioral detail beyond the annotation.

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 dense but purposeful, front-loading the core definition and using subsequent sentences to clarify parameters and alternatives. Some asides could be tightened, but every sentence adds relevant information.

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

Completeness4/5

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

The description covers the tool's purpose, key parameter semantics, data origin, and alternative tools, which is sufficient for an agent to call it correctly. The missing explanations for entity and limit are minor and partially offset by the schema's defaults and obvious naming.

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?

With 0% schema description coverage, the description compensates for the key parameters: period, with_text, and max_chars are explained with purpose and context. However, the required entity parameter and the limit parameter are not described, relying on their names and defaults for meaning.

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 identifies the tool as retrieving company press releases, specifically the EX-99 exhibits attached to 8-K filings. It distinguishes these from newswire summaries and from get_filings(kind='events'), making the resource and scope unambiguous.

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 explicitly explains when to use with_text, what period does ('return that year's earnings releases instead of the latest'), and directs the agent to get_filings(kind='events') for the filed-event view. This provides strong, actionable routing against sibling tools.

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

All OptimistFi 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?