NetNest Design Fundamentals API

One metric over time

get_history

Read-onlyIdempotent

Financial history of one metric from SEC filings, newest first: revenue history, net income history, EPS history, cash flow history and more, by year, quarter or trailing twelve months. Up to 200 periods, each with its 10-K or 10-Q, filing date and SEC link.

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>",
      "metric": "<metric>"
    },
    "name": "get_history"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of periods, newest first, 1 to 200 (default 20)
`metric`	Yes	The metric to return: 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
`period`	No	annual, quarterly or ttm (trailing twelve months)
`ticker`	Yes	Stock ticker, for example AAPL or BRK.B

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results are newest-first, capped at 200 periods, and each period carries its 10-K/10-Q type, filing date, and SEC link — useful for planning output handling.

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?

Two dense but efficient sentences; the core scope (one metric, SEC filings, newest first) is front-loaded and the return-shape details follow. The long metric enumeration is slightly redundant with the schema's enum but does reinforce the surface area at a glance.

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 no output schema, the description must carry the return contract, and it does — periods, filing type, filing date, SEC link, ordering, and cap. Only the absence of explicit sibling routing keeps it from being fully complete for an agent choosing among six tools.

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 the schema already documents ticker format, metric enum values, period values, and the 1–200 limit with default 20. The description's mention of 'by year, quarter or trailing twelve months' and 'up to 200 periods' mirrors rather than extends the schema, so this sits at the baseline.

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 precise verb+resource ('Financial history of one metric from SEC filings') and enumerates the metric families and period granularities, so the agent knows exactly what is returned. It does not name or contrast with siblings like get_fundamentals, leaving the historical-vs-point-in-time distinction implicit rather than stated.

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 implied — you call this when you need one metric's time series — but there is no explicit when-to-use clause, no exclusions, and no reference to get_fundamentals or get_company as alternatives for different needs. An agent must infer the routing decision from the sibling names alone.

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?