Skip to main content
Glama

Trading Signals Toolkit

Pre-Trade Check (bundle)

pre_trade_check
Read-only

One GO / CAUTION / NO_GO event-risk status with plain reasons for a futures contract: event-risk calendar check + session context (US macro calendar, Treasury yields, CFTC positioning, holidays) + SEC Form 4 insider activity (for ticker, else top market-wide insider clusters) + optional Base token verdict (token). 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": "pre_trade_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoOptional Base ERC-20 token address: adds an A-F token safety verdict
symbolYesFutures root: ES (E-mini S&P 500), NQ (E-mini Nasdaq-100), CL (WTI crude), GC (gold), ZN (10-year T-note)
tickerNoOptional US equity ticker (e.g. AAPL): adds its SEC insider buys
windowNoLook-ahead window in minutes (1-240, default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, idempotentHint=false, so safety framing is partly redundant. The description still earns credit by disclosing the fan-out composition (which upstream data sources are consulted) and by clarifying that the ticker path falls back to market-wide insider clusters when no ticker is supplied — behavior an agent cannot see from the schema. It omits latency expectations, partial-failure behavior when one source is unavailable, and caching, which matters for a multi-source bundle.

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

Conciseness5/5

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

Front-loaded with the output artifact and the verdict scale, then the component list, then the scope disclaimers. The parenthetical enumeration is dense but every element is a distinct data source an agent needs to know it gets, and there is no 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?

With no output schema, the description does the work of describing the return shape (a single status plus plain reasons) and the inputs that shape it. For a four-source bundle it is complete enough to call correctly, with only the `window` semantics and degradation behavior left implicit.

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?

Schema description coverage is 100%, so the baseline is 3; the description goes beyond that by explaining the conditional relationship between parameters: ticker drives SEC Form 4 insider activity, otherwise top market-wide clusters appear, and token adds a Base token verdict. The one gap is `window`, which the description never mentions even though it materially shapes the event-risk look-ahead.

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 output (a single GO / CAUTION / NO_GO event-risk status with plain reasons) for a specific resource (a futures contract), and then enumerates exactly what the bundle aggregates: event calendar, session context, SEC Form 4 insider activity, and an optional token verdict. That enumeration is what separates it from the single-purpose siblings like event_gate, session_brief, insider_buys, or token_pre_trade.

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 context is implied by 'pre-trade check' and by the fact that it bundles the individual sibling tools, so an agent can infer it is the one-call aggregate. However, it never says explicitly when to prefer this over calling event_gate or session_brief separately, nor does it state the cost/latency tradeoff of the bundle. The only explicit guidance is negative scope: 'Read-only, never places orders' and 'not investment advice'.

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