NetNest Design Fundamentals API

Latest values of chosen metrics

get_fundamentals

Read-onlyIdempotent

Latest company revenue, net income, EPS, operating income, assets, liabilities, equity, cash, operating cash flow, capex, free cash flow or shares outstanding from SEC filings. Choose metrics and period (annual, quarterly or ttm). Latest values follow the fiscal year of each company, with the source filing, filing date and accession number for every number.

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

Input Schema

Name	Required	Description
`period`	No	annual, quarterly or ttm (trailing twelve months)
`ticker`	Yes	Stock ticker, for example AAPL or BRK.B
`metrics`	No	Comma separated: revenue, net_income, eps_basic, eps_diluted, operating_income, total_assets, total_liabilities, equity, cash, operating_cash_flow, capex, free_cash_flow, shares_outstanding, revenue_contract

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: values follow each company's fiscal year, and every number carries its source filing, filing date and accession number.

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. The metric scope is front-loaded and the fiscal-year and provenance caveats land immediately after, so the agent gets the important nuance without scanning.

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?

There is no output schema, but the description compensates by saying each number is returned with its filing, filing date and accession number, and by clarifying the fiscal-year alignment. Only the response shape (flat vs. keyed by metric) remains unspecified.

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, including the valid metric tokens and the annual/quarterly/ttm values. The description restates the period options and metric names without adding syntax or default guidance beyond the 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?

Names a specific resource (latest fundamentals from SEC filings) and enumerates the metric families covered, so the agent knows exactly what comes back. It never names a sibling, though the word 'Latest' implicitly contrasts with get_history without saying so.

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: 'Choose metrics and period' tells the agent what to supply but not when this tool is preferred over get_history or get_company. No exclusions or alternative routing are stated.

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

All NetNest Design Fundamentals API 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?