Equibles

Earnings Brief

GetEarningsBrief

Read-only

Get the AI 'Earnings Brief' for a company's recent earnings calls — a verifier-approved TL;DR, bullish and bearish points, and verbatim pull-quotes, plus a deterministic narrative shift against the immediately older available approved brief. When available, it also shows company guidance issued at the call, how that range changed from management's prior update, and the reported quarter versus the operative company guidance that preceded it. This is company guidance, not analyst consensus; actual comparisons use filed GAAP XBRL facts, never estimates. The shift is derived from approved bullets and is not separately verifier-approved. Newest quarter first. Only calls with an approved brief appear, so quarters can be missing from the sequence.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of quarterly briefs to return, newest first (default 2, max 8; values outside 1-8 are clamped)
`ticker`	Yes	Company ticker symbol (e.g., AAPL, MSFT), or MIC:TICKER (e.g., XPAR:AIR) for a listing outside the US.
`fiscalYear`	No	Company fiscal year. Omit both period fields for newest briefs; year alone filters that fiscal year.
`fiscalQuarter`	No	Company fiscal quarter, 1-4. Quarter alone filters that quarter across fiscal years; both fields select an exact period.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / ticker / description

Previous value: -"Company ticker symbol (e.g., AAPL, MSFT)"New value: +"Company ticker symbol (e.g., AAPL, MSFT), or MIC:TICKER (e.g., XPAR:AIR) for a listing outside the US."

Changed2 schema fields changedAug 27, 2026

changedInput schema / properties / fiscalQuarter / description

Previous value: -"Optional fiscal quarter, 1-4, to fetch a specific period's brief (default: newest first)"New value: +"Company fiscal quarter, 1-4. Quarter alone filters that quarter across fiscal years; both fields select an exact period."

changedInput schema / properties / fiscalYear / description

Previous value: -"Optional fiscal year, in the company's own fiscal calendar, to fetch a specific period's brief (default: newest first)"New value: +"Company fiscal year. Omit both period fields for newest briefs; year alone filters that fiscal year."

First observedJul 19, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Well beyond the annotations, the description discloses provenance and caveats an agent must know: the brief is verifier-approved, the narrative shift is NOT separately verifier-approved, guidance is company guidance rather than analyst consensus, and comparisons use filed GAAP XBRL facts and never estimates. It also warns that quarters can be missing from the sequence when no approved brief exists.

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?

Front-loaded with what the tool returns, then caveats. Each sentence carries distinct information (content, guidance behavior, provenance limits), though the single dense paragraph packs a lot and could be split for scanability.

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?

With no output schema and four parameters, the description fully covers what is returned, the trust level of each component, the comparison methodology, and the sparse-data caveat. An agent has everything needed to call it correctly and interpret the result.

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 already 100%, so the baseline is 3, but the description adds real meaning: 'Newest quarter first' corroborates ordering intent behind limit, and 'quarters can be missing from the sequence' explains why fiscalYear/fiscalQuarter filtering may return gaps. It adds context without restating field syntax.

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 names a specific verb and resource ('Get the AI Earnings Brief for a company's recent earnings calls') and enumerates the exact payload — verifier-approved TL;DR, bullish/bearish points, verbatim quotes and a derived narrative shift. That content profile makes it distinguishable from near-siblings like GetEarningsCallTranscript, GetEarningsCallToneAndThemes and GetGuidance without needing to name them.

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?

Usage is implied rather than stated: 'Only calls with an approved brief appear' and 'Newest quarter first' hint at when results will be sparse, but it never says when to prefer this over GetEarningsCallTranscript, GetEarningsCallToneAndThemes or GetGuidance. No explicit when/when-not or alternative routing is given.

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

All Equibles tools Inspect

Try in Browser