Skip to main content
Glama

SquawkFlow Market Structure

Market-implied probability that a level is exceeded by an expiration

get_implied_odds
Read-onlyIdempotent

Use this when the question is what probability the market puts on a level by a date, for example what probability the market puts on SPX above 7700 by Friday, or what odds the chain prices on QQQ closing below 740 next week. Returns the priced probability of settling above and below that level, an independent cross-check of the same number, a ladder of levels around the forward, and the implied distribution with its median, quartiles and central band, which is the options-implied expected move to that expiration. Coverage: SPX, SPY and QQQ only. One expiration per call, and only expirations settling within 90 days. Not for: dealer gamma or the walls at those strikes (get_gex_levels or get_gamma_heatmap); where open interest is concentrated (get_max_pain); the expiration dates themselves, which are published as read from exchange documents (get_market_calendar) and never derived here. Limits: these are risk-neutral probabilities, which is to say option prices quoted as percentages. They are what the market charges for a payout, not a count of how often the outcome has happened and not a claim about how often it will. Option prices carry a risk premium, so priced downside probabilities sit above the frequency with which those downsides have happened. Not a forecast and not a price target. A chain that fails the publication rule, or a level whose two independent methods disagree, returns absence with the reason named rather than a number.

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

Input Schema

NameRequiredDescriptionDefault
levelNoThe price level the question is about, for example 7700. Omit for the implied distribution and the ladder of levels around the forward without a single highlighted level.
symbolNoSPX, SPY or QQQ. Defaults to SPX. Any other symbol returns the SPX answer plus a coverage note.
expirationNoOptional ISO expiration date. Omit for the nearest expiration. Must be one of the servableExpirations the result lists.

Output Schema

NameRequiredDescriptionDefault
kindYes
pageYes
toolYes
notesYes
staleNo
tableNo
titleYes
usageNo
sourceYes
metricsYes
versionYes
capturedAtNo
source_urlNo
staleSinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / page / properties / linkLabel
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / source_url
      Added value: +{
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / usage
      Added value: +{
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedOutput schema / properties / page / properties / url
      Added value: +{
      +  "type": "string"
      +}
  5. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a read-only, idempotent, non-destructive, open-world read; the description adds substantial context beyond them: symbol coverage, the 90-day expiration bound, one-expiration-per-call, and the risk-neutral/risk-premium caveat that priced downside probabilities sit above realized frequencies. It also discloses the failure mode — a chain failing the publication rule or two methods disagreeing returns absence with the reason named rather than a number — which is exactly the kind of behavior an agent cannot infer from annotations.

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 structure is strong and front-loaded: purpose, examples, returns, coverage, exclusions, limits, failure behavior in that order, with no burying of constraints. It is on the long side and the restatement of risk-neutral probabilities ('which is to say option prices quoted as percentages') slightly doubles back, but nearly every sentence carries routing or interpretation value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 no further explanation, and the description still names the payload shape at a high level. For a zero-required-parameter, read-only analytic tool it covers eligibility, alternatives, interpretive limits and error behavior — nothing an agent needs in order to call it or read its result correctly appears missing.

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 100%, so the schema already documents level, symbol and expiration, establishing the baseline of 3. The description goes beyond it by framing what a level means in the answer, stating the symbol coverage rule and the 90-day settlement constraint, and clarifying that omission of a level still yields the distribution and ladder — details that shape how the parameters should be chosen, not just their types.

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 opens with a precise conditional purpose statement plus two concrete worked examples (SPX above 7700 by Friday, QQQ closing below 740 next week), then names exactly what is returned: priced probability above/below, an independent cross-check, a level ladder, and the implied distribution with median, quartiles and central band. It is unmistakably distinct from get_gex_levels, get_gamma_heatmap and get_max_pain because those are explicitly excluded.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies an explicit 'Use this when' trigger, a 'Not for' block naming three sibling alternatives with the subject each actually covers, and hard eligibility rules (SPX/SPY/QQQ only, one expiration per call, expirations within 90 days). It also notes where expiration dates come from (get_market_calendar, read from exchange documents, never derived here), so an agent can route correctly before calling.

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