Skip to main content
Glama

HPSILab Quant Finance

Options Pressure Map

get_option_pressure
Read-onlyIdempotent

Option-chain pressure map for the nearest weekly/monthly expiry — Max Pain, dealer Gamma Wall, likely weekly high, and an extreme squeeze target.

Returns spot, the expiry and days to it, the option quote time (latest
trade in the chain, UTC), max pain, gamma/call/put walls, likely weekly
high, squeeze target, likely expiry close range, ATM IV and the weekly
expected move. Its expiry can differ from get_iv_radar's.

Args:
    ticker: Stock symbol, e.g. "SPY".

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

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol, e.g. AAPL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ticker / description
      Added value: +"Stock ticker symbol, e.g. AAPL."
    • addedInput schema / properties / ticker / examples
      Added value: +[
      +  "AAPL"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real value beyond that by disclosing the return surface and the semantics of the option quote time (latest trade in the chain, UTC), which signals the data can be stale relative to spot.

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?

The purpose and the most decision-relevant fact (returned fields, expiry relationship) are front-loaded, and every sentence carries information. The "Args: ticker" block is redundant with a fully documented schema and is the one piece of waste.

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 no output schema, the enumeration of returned values (spot, expiry, DTE, quote time, max pain, walls, ranges, ATM IV, expected move) is the right compensation and makes the tool callable without surprises. It stops short of describing units or sign conventions for walls, which would have completed it.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents ticker fully. The description only restates the example ("SPY" vs the schema's "AAPL") and adds no format constraints or symbol-resolution rules, so baseline 3 applies.

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 names a specific resource and scope — an option-chain pressure map for the nearest weekly/monthly expiry — and enumerates the distinctive outputs (Max Pain, dealer Gamma Wall, weekly high, squeeze target). It also explicitly distinguishes itself from a sibling by noting its expiry can differ from get_iv_radar's.

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 implied by the content (options positioning, max pain, gamma walls) and there is a useful disambiguation note that the expiry may differ from get_iv_radar's. However, it never states when to prefer this tool over get_iv_radar or other analytics siblings, nor any preconditions such as needing an options-enabled ticker.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.