Skip to main content
Glama

AINDEX

Upcoming earnings for stocks with a Robinhood token

get_earnings
Read-only

Earnings over the next 1 to 14 days for the stocks that have a Robinhood token on this chain, with the token's address, whether before the open or after the close, and the EPS forecast; or one ticker's next earnings date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_earnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
tickerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real behavior beyond that — the universe is restricted to stocks with a Robinhood token on this chain, the horizon is capped at 14 days, and the returned fields (token address, open/close timing, EPS forecast) are disclosed. It does not discuss result ordering or behavior for tickers without a token, which keeps it out of 5 territory.

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?

A single dense sentence that front-loads the scope, the returned fields, and the alternative ticker mode with no filler. It is slightly hard to parse in one pass because the two modes are joined by 'or', but nothing is redundant.

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?

For a two-optional-parameter read tool with no output schema, the description covers the query scope, the horizon cap, and the shape of the results, which is enough to call it correctly. Minor omissions are the default of 7 days and whether the ticker mode ignores the days window.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the semantics, and it does: 'over the next 1 to 14 days' explains the days parameter and its bounds (minimum 1, maximum 14), while 'one ticker's next earnings date' explains the ticker parameter's effect on the response. That is meaningful compensation for the undocumented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Earnings over the next 1 to 14 days') plus the population it covers ('stocks that have a Robinhood token on this chain') and the payload fields (token address, before-open/after-close, EPS forecast), and names a second mode ('one ticker's next earnings date'). The only gap is that it doesn't distinguish this from the sibling 'earnings_release', which an agent could plausibly confuse with an earnings-calendar tool.

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?

The two modes (broad window of tokenized stocks vs. one ticker) implicitly signal when to use each, but there is no explicit 'use this instead of X' routing, no statement about the default 7-day window, and no note on what happens if both parameters are supplied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources