OpenNash Earnings

Get quarter

get_quarter

Read-onlyIdempotent

Get one quarter's results: headline, overview, reported figures with their source sentence, segments, outlook, a check of last quarter's outlook against what was reported, takeaways, management quotes and analyst Q&A.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_quarter"
  }
}

Input Schema

Name	Required	Description	Default
`ticker`	Yes	Stock ticker, such as NVDA
`quarter`	No	Fiscal quarter key from get_company, such as 2027-q2. Omit for the latest.

Output Schema

Name	Required	Description	Default
`q`	Yes
`fy`	Yes
`qa`	No
`key`	Yes
`url`	Yes
`filed`	Yes
`label`	Yes
`quotes`	No
`ticker`	Yes
`topics`	No
`metrics`	No
`guidance`	No
`headline`	No
`overview`	Yes
`segments`	No
`documents`	No
`questions`	No
`recording`	Yes
`takeaways`	No
`filing_url`	Yes
`period_end`	Yes
`guidance_check`	No
`has_transcript`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real behavioral context by disclosing that figures come with their source sentence and that the tool cross-checks last quarter's outlook against what was actually reported — a non-obvious derived output. It says nothing about volume, latency, or what happens when a quarter has no data, so the bar is met but not exceeded.

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 sentence, front-loaded with verb and scope, followed by a comma-delimited inventory of returned sections. The enumeration is long but every item earns its place by telling the agent what it will get. Slight readability cost from the run-on list, but no wasted prose.

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?

The tool has a full output schema and complete annotations, so the description only needs to orient the agent — which it does by naming the content categories returned. Combined with schema-documented parameters and a clear default for the quarter key, an agent has everything needed to call it correctly.

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 coverage is 100%: both the ticker example (NVDA) and the quarter key format with the 'omit for the latest' default are fully documented in the schema. The description adds no additional parameter meaning beyond that, so the baseline 3 applies.

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?

The description uses a specific verb ('Get') plus a clearly scoped resource ('one quarter's results') and then enumerates the payload (headline, reported figures with source sentence, segments, outlook, takeaways, quotes, Q&A). An agent can tell this is the single-quarter deep-dive tool. It stops short of naming how it differs from get_kpis or get_transcript, so it is clear but not sibling-differentiated.

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 only implied: the phrase 'one quarter's results' plus the enumerated contents signal that this is the full-quarter summary tool rather than the KPI-only or transcript-only ones. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer routing from the sibling list.

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

All OpenNash Earnings 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?