Skip to main content
Glama

Owner Earnings and ROIC

GetOwnerEarnings
Read-only

Get owner earnings and ROIC (return on invested capital) by fiscal year, oldest first: net income, depreciation and amortization, capital expenditures, owner earnings (net income + D&A - capex), an estimated maintenance versus growth capex split, and ROIC. Every reported figure is the latest filed value for exactly that fiscal year; ROIC is computed at the year's first filing date from the facts filed by then. The capex split is an estimate shown beside the headline figure, never inside it. A figure that is not on file or not provable is a dash, never an estimate. Owner earnings are computed for companies reporting in US dollars; a REIT is valued on FFO through GetValuationMultiples instead.

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": "GetOwnerEarnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoFiscal years to return, keeping the newest (default 5, max 10).
tickerYesStock ticker symbol (e.g., COST, AAPL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare a safe read (readOnlyHint/destructiveHint=false); the description adds substantial non-obvious behavior: figures are the latest filed value for exactly that fiscal year, ROIC is computed at the year's first filing date from facts filed by then, the capex split is an estimate shown only beside the headline number, and unprovable figures return a dash rather than an estimate. These are exactly the caveats an agent needs to interpret results correctly.

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?

The core resource and returned metrics are front-loaded, and every sentence carries substantive information with no filler. The sentences are long and clause-dense, which slightly reduces scannability for an agent parsing the definition quickly.

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, the description must explain the return shape, and it does so thoroughly: metric list, ordering, vintage semantics, estimate handling, and the dash-for-missing convention. It also discloses the USD-only scope limit and the alternative for REITs, leaving no material gap for correct invocation and interpretation.

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 100% and both parameters are already documented, so the schema carries most weight. The description still adds ordering semantics not present in the schema (results are oldest first) and clarifies that the capex split is presented alongside, not inside, the headline figure, which affects how the returned series should be read.

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?

Names a specific verb and resource (owner earnings and ROIC by fiscal year) and enumerates the exact figures returned: net income, D&A, capex, owner earnings, maintenance-vs-growth capex split, and ROIC. It also names the sibling it is not for (REITs → GetValuationMultiples), so an agent can separate it from other financial siblings without opening the schema.

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 routing rule with an alternative: REIT valuation belongs in GetValuationMultiples, not here, and the USD-reporting constraint is stated. It does not spell out positive when-to-use conditions (e.g., vs. GetEarningsBrief or GetValuationMultiples for non-REITs), so it stops short of full exclusion coverage.

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.