Skip to main content
Glama

Trading Signals Toolkit

AI Trade Brief

ai_trade_brief
Read-only

AI-written summary of the toolkit's own market data for ES/NQ/CL/GC/ZN (event-risk calendar check, session context, Treasury yields, CFTC positioning, SEC insider activity, and the macro event study for the next high-impact release): headline, summary, upcoming catalysts in ET, key reference levels, risk factors, a deterministic event-risk status (GO/CAUTION/NO_GO), and the input facts. If the AI upstream is unavailable the call fails. 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": "ai_trade_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceNoOptional current futures price so typical move sizes can be shown as price levels
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. Changed1 schema field changed
    • changedInput schema / properties / price / description
      Previous value: -"Optional current futures price, so typical moves and stops can be expressed as levels"New value: +"Optional current futures price so typical move sizes can be shown as price levels"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already carry readOnlyHint/ destructiveHint/ openWorldHint, so the safety profile is covered; the description still adds real value by disclosing the failure mode ('if the AI upstream is unavailable the call fails') and the deterministic GO/CAUTION/NO_GO element. It does not explain why the call is non-idempotent (idempotentHint=false) or whether output varies between calls, which is a meaningful gap for an LLM-generated result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded but the opening sentence is a long run-on wrapping a seven-item parenthetical, which makes it dense to parse. The trailing short sentences ('Read-only, never places orders', 'Informational only') are partly redundant with annotations and could be tightened.

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?

With no output schema, the description usefully enumerates the return payload (headline, summary, catalysts in ET, reference levels, risk factors, status, input facts), so an agent knows what comes back. The one notable gap is that the look-ahead 'window' parameter's relationship to the catalyst scan is never explained.

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 description coverage is 100% and each parameter is documented in-schema (symbol enum with expansions, window range/default, price purpose). The description adds nothing about parameters, not even what the window applies to, so it sits at the baseline rather than above it.

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 verb and resource ('AI-written summary of the toolkit's own market data') and enumerates the data sources and output contents, so the agent knows exactly what it produces. It does not explicitly differentiate itself from siblings like session_brief or event_gate, leaving the aggregation-vs-single-source distinction implicit.

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 description makes clear this is a composite brief pulling from several datasets, but never says when to call it instead of the narrower sibling tools (session_brief, cot_screener, insider_buys, event_gate) or that they are bundled here. No exclusions or prerequisites are given beyond 'AI upstream must be available'.

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