Option Desk

Option plots

option_plots

Read-onlyIdempotent

Render opaque PNG plots in the conversation. The SYNTH sample offers the market plot (dealer gamma exposure, open interest, volume and the smile by strike), the Greek ladder, and the structure comparison. Each is computed from the sample's own engine artifacts; there is no simulation or backtest for SYNTH because the hosted service has no price history.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "option_plots"
  }
}

Input Schema

Name	Required	Default
`plot`	No	all
`rate`	No
`expiry`	No
`symbol`	No	SYNTH
`data_source`	No
`source_data`	No
`source_text`	No
`source_format`	No
`dividend_yield`	No
`rights_confirmed`	No

Output Schema

Name	Required	Description
`units`	No
`expiry`	Yes	Option expiry, when available.
`images`	No	The returned images, for the inline plot app.
`warning`	Yes	Data and financial-risk warning.
`strategy`	Yes	Requested strategy for a payoff plot, when applicable.
`data_mode`	Yes	Whether the figures are synthetic or user supplied.
`plot_types`	Yes	Plot names in the same order as the image content.
`underlying`	Yes	Underlying shown by the plots.
`captured_at`	Yes	Snapshot or fixture timestamp, when available.
`data_source`	Yes	Named source used for the figures.
`diagnostics`	No
`expiry_note`	No	Set when the requested expiry is not the one the figures are for.
`image_count`	Yes	Number of returned PNG images.
`strategy_records`	No	Exact plotted engine records. Use these for tables; do not infer values from images.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 11, 2026

TDQS

B3.3/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 behavior, so the bar is lower. The description adds real context beyond them: output is an opaque PNG (not an interactive or structured chart), the plots derive from the sample's own engine artifacts, and the SYNTH sample lacks price history so no simulation or backtest exists.

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?

Three sentences, front-loaded with the core action and the available plot types, with the SYNTH caveat following. The engine-artifact and no-backtest sentences both earn their place, though the wording is slightly repetitive around the SYNTH limitation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is high-complexity (10 parameters, 0% schema coverage), and although an output schema exists so return values need not be explained, the description leaves most inputs opaque. An agent could not confidently supply source_data, source_format, or rights_confirmed from this text.

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 description coverage is 0% across 10 parameters, so the description carries the full burden. It only clarifies the plot selector (matching the 'market'/'greeks'/'strategy_comparison' enum values) and the SYNTH symbol default; rate, expiry, data_source, source_data, source_text, source_format, dividend_yield, and rights_confirmed are entirely unexplained.

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 verb and resource ('Render opaque PNG plots in the conversation') and enumerates the three plot families it produces (market, Greek ladder, structure comparison). It does not distinguish itself from siblings such as option_plots_from_snapshot or option_strategy_plot, so an agent cannot tell from this text alone which plot tool to pick.

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: the description establishes that this tool serves the SYNTH sample and that no simulation or backtest is available for it because the hosted service has no price history. There is no explicit when-to-use or when-not-to-use statement, and no named alternative for snapshot-based or strategy-specific plotting.

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

All Option Desk 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?