Skip to main content
Glama

AINDEX

Options positioning

options_intel
Read-only

BTC, ETH or SOL options: max pain and dealer gamma by strike for one expiry (the largest within 45 days unless given), ATM implied volatility by expiry, 25-delta skew, put/call open interest, and the largest recent trades. Deribit first, Bybit when Deribit does not answer.

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

Input Schema

NameRequiredDescriptionDefault
expiryNo
currencyNoBTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real context beyond them: the provider fallback chain ('Deribit first, Bybit when Deribit does not answer') and the default expiry-selection rule, both of which affect how results should be interpreted. It does not discuss latency, rate limits, or what happens when neither provider answers, so it is not a 5.

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 output inventory is front-loaded in a single dense sentence, followed by a short provider-fallback sentence. Every clause carries information; the comma-list of outputs is long but each item is a distinct capability. Slightly denser than ideal, but no wasted words.

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 description compensates by listing the returned metrics, which is exactly what an agent needs to judge relevance. Combined with the read-only annotations and the two-parameter schema, the definition is nearly self-sufficient. The missing expiry-format guidance and failure behavior when both providers are unavailable are the only notable holes.

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?

Schema description coverage is 0%, so the description must carry the burden. It explains the default behavior for expiry (largest within 45 days) and confirms the currency set, which is meaningful. It never explains the accepted expiry string formats (YYYY-MM-DD or DDMMMYY) or what happens with an invalid/past expiry, leaving a real gap at low schema coverage.

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?

The description names the exact resource (options positioning for BTC, ETH or SOL) and enumerates the specific outputs: max pain, dealer gamma by strike, ATM implied volatility by expiry, 25-delta skew, put/call open interest, and largest recent trades. An agent can distinguish this from generic siblings like get_derivatives. It stops short of explicitly contrasting itself with any named alternative, which keeps it at 4 rather than 5.

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?

It states an important usage rule: a single expiry is analyzed, defaulting to the largest within 45 days unless one is supplied. That is genuinely useful selection guidance for the expiry parameter. However, there is no when-to-use vs when-not framing and no sibling alternative is named, so the guidance is implied rather than explicit.

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.

Resources