DataPorium

get_options_chain

Read-onlyIdempotent

Option chain (calls and puts with strikes, expirations, prices, volume, open interest) for a stock.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_options_chain"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Ticker symbol, e.g. AAPL, MSFT or NVDA. Use search_symbols if you only know the company name.
`filters`	No	Optional extra filters as a JSON object of API parameter names and values, e.g. {"fiscal_year": 2025}. Call list_filters with this tool's name to see every accepted filter.

Output Schema

Name	Required	Description
`data`	No	The records: a list of objects (or one object) with the requested data.
`note`	No	Present when the answer was shortened, with how to get the rest.
`rows`	No	Number of records the API returned (before any shortening).
`error`	No	Present when the call failed, with the reason.
`detail`	No	Extra error detail from the API, e.g. which filter is required.
`paging`	No	For paged answers: offset, rows_shown, total and next_offset (call again with offset=next_offset for more rows).
`endpoint`	No	DataPorium API endpoint that answered, e.g. /company-info.
`filters_sent`	No	Filters sent to the API for this answer.
`allowed_filters`	No	On an unknown-filter error: the filters this endpoint accepts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

addedOutput schema / properties / paging

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "For paged answers: offset, rows_shown, total and next_offset (call again with offset=next_offset for more rows).",
+  "title": "Paging"
+}

First observedSep 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is fully covered. The description adds the shape of the returned data, but says nothing about auth, rate limits, or size/cost of pulling a full chain. With annotations carrying the safety burden, this is adequate but thin.

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?

A single front-loaded sentence that names the resource, its scope, and its contents with zero filler. Nothing is wasted.

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, return values need no elaboration, and annotations cover the safety profile. The description is nearly complete; only usage/routing context is missing for a tool with a rich output.

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 coverage is 100%, so both symbol and filters are already documented in the schema, including the pointer to list_filters. The description adds no parameter-level detail, which is the correct baseline when the schema does the heavy lifting.

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?

States a specific resource (option chain) scoped to a stock and enumerates its contents (calls/puts, strikes, expirations, prices, volume, open interest). No close sibling exists to differentiate from, so the lack of explicit routing is not a real gap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no when-to-use guidance, prerequisites, or alternatives. The schema mentions search_symbols for name-to-ticker lookup, but that hint lives in the schema rather than the description, leaving usage entirely to inference.

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

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