OpenNash Earnings

Get company

get_company

Read-onlyIdempotent

Get a company's profile and every quarter we have, newest first, with quarter keys for get_quarter.

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_company"
  }
}

Input Schema

Name	Required	Description	Default
`ticker`	Yes	Stock ticker, such as NVDA

Output Schema

Name	Required	Description	Default
`ir`	No
`cik`	Yes
`url`	Yes
`name`	Yes
`sector`	No
`ticker`	Yes
`exchange`	No
`quarters`	Yes
`legal_name`	No
`next_expected`	No
`fiscal_year_end`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior beyond that: the result ordering ('newest first'), the coverage caveat ('every quarter we have' rather than every quarter that exists), and the presence of usable quarter keys for chaining into get_quarter.

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?

One compact sentence that front-loads the resource and then the payload and ordering. Nothing is wasted and no clause 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?

With an output schema present, the description need not enumerate return fields, and the key behavioral facts (ordering, quarter key purpose, coverage limit) are given. It is slightly thin on what the 'profile' comprises or what happens for an unknown ticker, but it is adequate for a one-parameter read.

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?

There is a single parameter (ticker) with 100% schema description coverage, including an example. The description adds no further meaning about the ticker's format or case sensitivity, 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 gives a specific verb ('Get') and resource ('a company's profile') and adds the scope of the return payload ('every quarter we have, newest first'). It also implicitly distinguishes itself from get_quarter by noting the returned quarter keys feed that sibling, though it never names alternatives like list_companies or search.

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: you call this to fetch a company profile plus its quarter list, and the returned quarter keys are meant for get_quarter. There is no explicit when-to-use or when-not guidance, and no stated alternatives for looking up a company by name versus ticker.

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?