Option Desk

Plots from snapshot

option_plots_from_snapshot

Read-onlyIdempotent

Create opaque market and Greek PNG images from a user-supplied snapshot. Stamp source, capture time, expiry, and warnings on every image. Delete temporary files before the response.

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": "option_plots_from_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`rate`	No
`expiry`	No
`symbol`	Yes
`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, closed-world, and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: every image is stamped with source, capture time, expiry, and warnings, and temporary files are deleted before the response returns. What is missing is any mention of a prerequisite or gating condition, which matters given the unexplained rights_confirmed flag.

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 short sentences, front-loaded with the output artifact, each carrying distinct information (creation, stamping, cleanup). Slightly marked down because 'opaque' is ambiguous terminology that the reader must guess at rather than a clarifying detail.

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?

An output schema exists, so return values need not be described, and the annotations are rich. However, for a 9-parameter tool with zero schema coverage, a description that never explains a single input — including the one required parameter and a boolean that appears to gate the call — is not complete enough to invoke reliably.

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 9 parameters, so the description carries the full burden and largely fails. 'Snapshot' and 'stamp source, capture time, expiry' loosely gesture at source_data/source_text/source_format and expiry, but symbol (required), rate, dividend_yield, data_source, and especially rights_confirmed receive no explanation at all — an agent cannot tell whether that boolean is a licensing gate or an optional toggle.

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 concrete verb and output artifact: 'Create opaque market and Greek PNG images from a user-supplied snapshot.' The 'from a user-supplied snapshot' clause implicitly separates it from the live-data sibling option_plots, but no sibling is named, so the differentiation is left to inference.

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?

The phrase 'from a user-supplied snapshot' implies the precondition (you must have snapshot data in hand), but there is no explicit when-to-use statement, no when-not-to-use case, and no routing to alternatives such as option_plots or option_strategy_plot. The agent must infer selection from the name alone.

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?