Trading Volatility MCP

Official

Overview Schema Source Related Servers Discussions Admin

get_levels

Fetch key price levels for any ticker: gamma flip, walls, max pain, and expected-move bounds. Choose output as JSON, TradingView, or thinkorswim.

Instructions

Get key price levels for a ticker (gamma flip, walls, max pain, expected-move bounds). Optional view formats the output: 'json' (default), 'tradingview', or 'tos' (thinkorswim).

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": {
      "ticker": "<ticker>"
    },
    "name": "get_levels"
  }
}

Input Schema

Name	Required	Description	Default
`view`	No
`ticker`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 1, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description must carry the transparency burden. It discloses the `view` parameter's effect on output formatting, but does not state whether the operation is read-only, the response structure, or any error conditions. The read-only nature is implied but not explicit.

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?

The description is two concise sentences, front-loading the core purpose and then providing essential format details. No redundant or irrelevant information.

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 two-parameter, read-oriented tool with an output schema, the description covers the essential aspects: what levels are returned, which parameters control the call, and output formatting options. It lacks usage context, but that is scored separately.

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?

Schema coverage is 0%, so the description compensates by explaining both parameters: `ticker` is the symbol to query, and `view` formats the output with allowed values. It adds the default ('json') and explains the purpose of each parameter, which is beyond the schema's bare type definitions.

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 clearly states the tool's function: retrieving key price levels for a ticker, and enumerates specific level types (gamma flip, walls, max pain, expected-move bounds). This specificity distinguishes it from sibling tools that handle gamma curves or GEX by strike.

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?

No guidance is given on when to use this tool versus alternatives. The description focuses solely on mechanics (view options) and does not mention prerequisites, typical use cases, or when to prefer other tools like get_gamma_curve.

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

Deploy Server