OptimistFi

get_prices

Read-only

OHLCV bars for an entity (ticker/name/CIK), newest first.

live=True returns ONE live real-time quote instead of bars — latest trade plus today's
open/high/low, previous close, change and % change, from a single uncached vendor call (the
other arguments are ignored). Use it for "what is it trading at right now"; leave it False for
history. data.is_market_open flags whether the print is live or the last close.

interval: 1min · 5min · 15min · 30min · 1h · 1day · 1week · 1month (default 1day).
Intraday bars carry a full timestamp in event_time; daily and longer carry a date. How far
back intraday reaches is a function of the plan behind the key, not of this server.

Served under our own vendor license. Each record's source.license states what may be done
with it: "licensed" (redistribution-licensed), "internal" (dev/demo, do not redistribute),
or "byol" (caller's own entitlement). Bars are historical/EOD; pass live=True for a real-time
quote instead. Returns SCHEMA §2 envelopes of type "price" (or "quote" when live=True).

Input Schema

TableJSON Schema

Name	Required	Default
`end`	No
`live`	No
`limit`	No
`start`	No
`entity`	Yes
`interval`	No	1day

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses meaningful behavioral details: live=True makes a single uncached vendor call, other arguments are ignored, data.is_market_open indicates live vs last close, intraday bars use full timestamps while daily/longer use dates, and history depth depends on the caller's plan. It also explains license semantics per record. This is far more than annotations alone provide.

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 description is long but each section earns its place, and the core purpose is front-loaded. The live-vs-bars distinction, interval list, and license notes are all relevant. It is dense but not redundant, though it could be tightened slightly.

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?

For a tool with an output schema present, the description covers the main behavioral modes, interval options, license constraints, and plan-dependent behavior. The only notable omission is start/end/limit parameter semantics, which prevents a perfect score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It covers entity, live, and interval well, but start, end, and limit are entirely undocumented in both the schema and the description. An agent has no way to know the expected date format, range behavior, or how limit interacts with the result set. This is a significant gap for a 6-parameter tool.

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?

The description opens with a precise action and resource: 'OHLCV bars for an entity (ticker/name/CIK), newest first.' It also clearly distinguishes bars from the live quote mode, so an agent can tell exactly what the tool returns. This fully separates it from the many sibling get_* tools.

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?

The description explicitly says to use live=True for 'what is it trading at right now' and to leave it False for history, which is strong within-tool routing. It does not name alternative sibling tools, but the guidance is clear enough for correct selection and mode choice.

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

All OptimistFi 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?