AlphaYou: Smart Money Intel

Check futures positioning

get_futures_positioning

Read-only

Read up to eight stored CFTC futures-only reports for SPX (S&P 500), TY (10-year Treasury), WTI (crude oil) or GC (gold). Shows dated category long/short/net contract counts and open interest. TFF and disaggregated categories remain distinct. Weekly reported positions lag trading; no wallet identities, real-time flows, options chain or stock shares.

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": {
      "contract": "<contract>"
    },
    "name": "get_futures_positioning"
  }
}

Input Schema

Name	Required	Description	Default
`reports`	No	Weekly reports to return, 1 to 8
`contract`	Yes	S&P 500, 10-year Treasury, crude oil or gold

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 12, 2026
- addedInput schema / properties / contract / description
```
Added value: +"S&P 500, 10-year Treasury, crude oil or gold"
```
- addedInput schema / properties / reports / description
```
Added value: +"Weekly reports to return, 1 to 8"
```
First observedOct 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), so the description's job is to add behavioral context — and it does: a hard cap of eight reports, the fact that weekly reported positions lag trading, and that TFF versus disaggregated categories stay distinct. It does not state the response shape beyond the field list, but for a read-only tool this is materially useful added context.

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 core action and scope, and every sentence carries information (cap, content, taxonomy caveat, lag, exclusions). It is a dense single block with some compressed jargon ('TFF and disaggregated categories remain distinct') that could be split for readability.

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 two-parameter read-only tool with no output schema, the description covers what is returned, the maximum volume, the freshness caveat, and the data boundaries. Nothing an agent needs in order to call this correctly or interpret the staleness of results is missing.

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%, so both parameters are already documented, including the 1–8 range and the enum labels. The description restates the eight-report cap and expands contract tickers to asset names, but adds no new format or semantics beyond the schema — 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?

States a specific verb and resource ('Read ... stored CFTC futures-only reports') plus the exact covered universe (SPX, TY, WTI, GC) and the returned fields (dated category long/short/net counts and open interest). The negative scope ('no wallet identities, real-time flows, options chain or stock shares') separates it from the Hyperliquid positioning siblings without needing to name them.

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 rather than stated: the scope list (futures-only, these four contracts, lagged weekly data) tells an agent when this tool is appropriate and when it is not. However, no sibling is named and there is no explicit 'use X instead for real-time or wallet-level positioning' routing instruction.

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

All AlphaYou: Smart Money Intel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?