Skip to main content
Glama

SquawkFlow Market Structure

CFTC futures positioning: long, short and net by trader classification

get_positioning
Read-onlyIdempotent

Use this when the question is how index futures positioning is distributed across trader classifications: dealers and intermediaries, asset managers, leveraged funds, other reportables and nonreportables, with long, short, spreading and net contracts and the week history. Omit the contract to list the published pages. Coverage: the CFTC Traders in Financial Futures futures-only report for the index futures SquawkFlow publishes a page for. Weekly US government data, not a market feed. Not for: options positioning or dealer gamma (get_gex_levels); commodity futures, which this server does not publish; any reading of the session in progress. Limits: positions are held as of the stated Tuesday and published the following Friday afternoon, so this is a weekly picture that is three days old by construction. Net is long minus short in contracts, an arithmetic difference between two published counts, not a sentiment reading. Contract markets with different index multipliers are never added together.

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

Input Schema

NameRequiredDescriptionDefault
weeksNoWeekly readings of history to return, 1 to 52, oldest first.
contractNoA published page slug, for example sp500 or nasdaq100. Omit to list the pages. An unknown slug returns the list, never a similar page.

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.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds material context beyond that: the Tuesday-as-of / Friday-afternoon publication lag, the fact that net is an arithmetic long-minus-short difference rather than sentiment, and the rule that contracts with different index multipliers are never aggregated. Return shape is left to the output schema, which is acceptable.

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 the 'Use this when' trigger, then coverage, exclusions and limits in a logical order. Dense but every clause carries information; a few sentences are long and could be split, but nothing is padding.

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?

For a read-only weekly data lookup with an output schema, the description covers what it returns, its publication lag, its arithmetic semantics, aggregation caveats and sibling exclusions. An agent can decide to call it and interpret the numbers without further context.

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 coverage is 100%, and the schema itself already states that omitting contract lists pages and that an unknown slug returns the list rather than a similar page, so the description largely restates that. It adds no detail on the weeks parameter beyond 'the week history', leaving the schema to do the work — the expected baseline when the schema is complete.

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 (index futures positioning) and the exact breakdown (dealers/intermediaries, asset managers, leveraged funds, other reportables, nonreportables) with long, short, spreading and net contracts. It explicitly scopes the source to the CFTC Traders in Financial Futures futures-only report, which separates it from sibling tools like get_gex_levels.

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?

Opens with the triggering question ('how index futures positioning is distributed across trader classifications') and supplies explicit exclusions: options positioning and dealer gamma go to get_gex_levels, commodity futures are not published here, and in-progress session readings are out of scope. This is a full when/when-not/alternative routing.

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