Skip to main content
Glama

SquawkFlow Market Structure

Election market context: dated SPX movement, VX windows and clock

election_market_context
Read-onlyIdempotent

Use this when the question asks what the SPX chain prices for the first post-election session, which VX window includes Nov 3, or where the dated election week schedule is published. Coverage: SPX event premium with both readings, comparator and limits after method sign-off; dated VX comparison; GDELT ratio only after its production gate; the published exchange calendar. Not for: election outcomes, venue prices or polling arithmetic. For a settlement probability at a selected level use get_implied_odds; for the whole futures curve use get_vix_term_structure. Limits: risk-neutral prices are not forecasts. The straddle is a cross-check on the same quotes, not an independent estimate. Each source carries its own date.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / page / properties / linkLabel
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / source / const
      Previous value: -"Delayed Cboe chain, Cboe daily settlements and GDELT with their own dates"New value: +"Delayed option chain, official daily settlements and GDELT with their own dates"
  2. Changed2 schema fields changed
    • addedOutput schema / properties / page / properties / url
      Added value: +{
      +  "pattern": "^https:\\/\\/squawkflow\\.com\\/elections\\/2026\\?utm_[A-Za-z0-9_=&-]+$",
      +  "type": "string"
      +}
    • addedOutput schema / properties / source_url
      Added value: +{
      +  "pattern": "^https:\\/\\/squawkflow\\.com\\/elections\\/2026\\?utm_[A-Za-z0-9_=&-]+$",
      +  "type": "string"
      +}
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the safety profile is settled. The description adds genuine behavioral context beyond that: some readings are conditional ('after method sign-off', GDELT 'only after its production gate'), and it warns that risk-neutral prices are not forecasts and that the straddle is a cross-check rather than an independent estimate. It does not say what a caller receives when a source is gated or unsigned, which is the remaining gap.

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 with 'Use this when...', then coverage, exclusions, alternatives and limits in a predictable order with no filler sentences. Some phrasing is insider jargon ('both readings', 'method sign-off', 'production gate') that an unfamiliar agent cannot fully resolve, which keeps it short of top marks.

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?

An output schema exists, so return shape need not be explained, and with zero parameters the input surface is trivial. The description covers scope, exclusions, alternatives and interpretive limits for a multi-source, domain-heavy tool. What is missing is how the caller knows which of the covered sources actually came back usable in a given call.

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 the schema cannot be enriched and the baseline applies. The description correctly adds nothing spurious about inputs and instead spends its budget on scope and interpretation caveats.

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 enumerates the concrete resources it returns: dated SPX event premium, dated VX window comparison, GDELT ratio, and the published exchange calendar. It is specific enough that an agent knows it is not a pricing/odds tool, though the tool is a bundle of three loosely related datasets rather than a single verb+resource statement.

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?

Explicit when-to-use triggers are given (first post-election session SPX pricing, which VX window includes Nov 3, where the election week schedule is published), plus an explicit 'Not for' list excluding outcomes, venue prices and polling arithmetic. It names two alternatives with the condition that selects each: get_implied_odds for a settlement probability at a selected level, get_vix_term_structure for the whole futures curve.

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