Skip to main content
Glama

Trading Signals Toolkit

Futures Session Brief

session_brief
Read-only

Session brief for ES/NQ/CL/GC/ZN: upcoming US high-impact releases with ET times and minutes-to, latest/prior BLS values, Treasury 2y/10y/2s10s with daily change, CFTC COT net positioning with 3y percentile, holiday/early-close flags, and a safeToTrade verdict. Read-only, never places orders. Informational only, not investment advice.

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": {
      "symbol": "<symbol>"
    },
    "name": "session_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesFutures root: ES (E-mini S&P 500), NQ (E-mini Nasdaq-100), CL (WTI crude), GC (gold), ZN (10-year T-note)
windowNoLook-ahead window in minutes (1-240, default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is pre-supplied. The description reinforces that with 'never places orders' and 'informational only, not investment advice', and its content list hints at live/session-scoped data, but it does not explain freshness, latency, or why the call is non-idempotent, so it adds modest value beyond the annotations rather than substantial new behavioral 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?

The definition is essentially one front-loaded sentence plus a short disclaimer sentence, with the scope (which five roots) stated before the payload list. The enumerated content is dense but each item is a distinct deliverable, so little is wasted; the trailing legal disclaimer is the only borderline filler.

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?

No output schema exists, so the description must carry the return-value burden, and it does by listing every section of the brief including the safeToTrade verdict. Combined with annotations covering safety and open-world behavior, an agent knows what it will receive; the remaining gap is that nothing explains freshness/timing of the snapshot or how the verdict is derived.

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%: symbol carries an enum with per-root expansions and window carries a 1-240 range with a stated default of 30. The description's 'minutes-to' phrase loosely connects to the look-ahead window, but it adds no format or behavior detail for symbol or window beyond the schema, so the baseline 3 applies.

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?

States a specific resource (a session brief scoped to ES/NQ/CL/GC/ZN) and enumerates its contents: upcoming US high-impact releases with ET times, BLS latest/prior values, Treasury 2y/10y/2s10s with daily change, CFTC COT positioning with 3y percentile, holiday flags, and a safeToTrade verdict. That is concrete and distinguishable from single-domain siblings like treasury_desk or cot_screener, though it never names those siblings to sharpen the boundary.

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

Usage Guidelines2/5

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

Provides no when-to-use or when-not-to-use guidance and never points at alternatives; a reader cannot tell from the text whether to call this or the narrower tools such as event_gate, treasury_desk, or cot_screener for a given question. The only framing is disclaimers (read-only, never places orders, informational only), which are constraints rather than usage 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