Option Desk

Option Desk status

option_desk_status

Read-onlyIdempotent

Check the Option Desk data mode, source, refresh time, and public licence gate before requesting figures. No live feed or hosted backtest tool exists, even with uploaded history. Do not offer hosted backtests.

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_desk_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 11, 2026

TDQS

A4.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, so the safety profile is covered. The description adds genuinely useful non-obvious behavior: there is no live feed, uploaded history does not unlock hosted backtests, and access is gated by a public licence check.

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?

Front-loaded and compact at three sentences, with the purpose first and the constraints after. The final sentence ('Do not offer hosted backtests') partially restates the prior one, but it reframes the fact as an instruction to the agent, which is arguably worth the repetition.

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?

Return values are covered by an existing output schema and the tool takes no arguments, so the description's job is mainly to set expectations. It does that well by flagging the licence gate and the absence of live/hosted capabilities, though it doesn't say what a gated or degraded status should prompt the agent to do next.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the empty schema. Baseline 4 applies; nothing is missing or misleading.

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?

States a specific verb (Check) and resource (Option Desk) plus the exact fields surfaced: data mode, source, refresh time, and public licence gate. It also carves out capability boundaries (no live feed, no hosted backtest), which lets an agent separate it from the snapshot/plot siblings without opening a schema.

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?

Gives a clear trigger condition: call it before requesting figures. It also adds an explicit don't-do: never offer hosted backtests, even with uploaded history. It stops short of naming which sibling to call for a given data need, which keeps it from a 5.

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?