Skip to main content
Glama
Sign In

Helious market intelligence

by io.helious
OverviewDiscussionsAdmin

Mega-cap earnings dates and EPS

get_earnings
Read-onlyIdempotent

US mega-cap earnings: when a company reports, whether that date is confirmed or still an estimate, whether it prints before the open or after the close, the consensus EPS, and once it lands the reported EPS with the beat or miss. Pass symbol for one name, like AAPL. This is the tool for any question about a company's earnings date or EPS.

Input Schema

NameRequiredDescriptionDefault
freshNoSet true to ask for the live view of this one call, for 5 credits, where the connected account otherwise receives it an hour behind. Accepted and free where the account is already live. No effect without a key.
limitNoMost rows to return.
symbolNoOne or more tickers, comma separated, like AAPL or AAPL,MSFT. Empty returns every name tracked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fresh / description
      Previous value: -"Not on Pro or Ultimate? Set this to true and this one call answers live for 5 credits. Left out, Free, Squawk and Starter get the answer an hour behind for 1 credit. Pro and Ultimate are live already, so it costs nothing extra there. No effect without a key."New value: +"Set true to ask for the live view of this one call, for 5 credits, where the connected account otherwise receives it an hour behind. Accepted and free where the account is already live. No effect without a key."
  2. Changed1 schema field changed
    • addedInput schema / properties / fresh
      Added value: +{
+  "description": "Not on Pro or Ultimate? Set this to true and this one call answers live for 5 credits. Left out, Free, Squawk and Starter get the answer an hour behind for 1 credit. Pro and Ultimate are live already, so it costs nothing extra there. No effect without a key.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description goes beyond that by disclosing output semantics an agent could not infer: confirmed-vs-estimate status, BMO/AMC timing, and consensus-vs-actual EPS with beat/miss — genuinely useful for deciding when to call it. It does not mention the paid 'fresh' path described in the schema, which is the one behavioral gap.

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?

Two sentences, zero filler, front-loaded with the returned fields and finished with an explicit scope statement. Every clause carries information the agent needs.

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?

With no output schema, the description does the heavy lifting by enumerating return fields, which is the main completeness requirement here. All three parameters are schema-documented and the tool is read-only, so remaining gaps (default behavior when symbol is omitted, limit/paging) are minor and covered by the schema itself.

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 description coverage is 100%, so all three parameters are already documented, and the description only restates the symbol parameter's format ('AAPL'). It adds no guidance on limit or on the fresh/credit trade-off beyond what the schema says, so the baseline 3 applies.

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 resource (US mega-cap earnings) and enumerates exactly what is returned: report date, confirmed vs estimate, before-open/after-close, consensus EPS, and reported EPS with beat/miss. The closing sentence ('This is the tool for any question about a company's earnings date or EPS') pins the scope unambiguously, and no sibling covers earnings, so there is nothing to confuse it with.

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 a clear positive usage rule — 'Pass symbol for one name, like AAPL' — and implies the unfiltered case by describing the tool as covering companies generally. It stops short of naming when NOT to use it or pointing at an alternative (e.g. a broader market-context sibling), so it is clear context without exclusions.

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

All Helious market intelligence toolsInspect
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