Skip to main content
Glama

Trading Signals Toolkit

Event-Risk Gate

event_gate
Read-only

safeToTrade verdict plus the next high-impact US release (BLS CPI/NFP/PPI, FOMC, Treasury auctions) within a minutes window. US public-domain agency data. Read-only, never places orders. Informational only, not investment advice.

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": "event_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNoLook-ahead window in minutes (1-240, default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only and non-destructive, so the bar is lower, but the description adds real context: it never places orders, the source is US public-domain agency data, and output is informational only. What is missing is behavior for the empty case (no qualifying event in window) and what the verdict is derived from.

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 core capability is front-loaded in the first sentence with zero preamble, and the event list is efficiently parenthetical. A small amount of boilerplate ('US public-domain agency data' / 'Informational only, not investment advice') partially overlaps with the read-only statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining returns, yet it never says what fields the verdict contains or how to interpret a non-safe result. For a single-parameter tool this is a moderate gap rather than a blocking one.

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 the single 'window' parameter already documents range and default, so the schema does the heavy lifting. The description's phrase 'within a minutes window' confirms intent but adds no format, edge-case, or interpretation detail beyond the schema.

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 concrete deliverable: a 'safeToTrade verdict plus the next high-impact US release ... within a minutes window', with named event classes (BLS CPI/NFP/PPI, FOMC, Treasury auctions). That is a specific verb+resource and lets an agent tell it apart from generic context tools like session_brief or treasury_desk. It stops short of explicitly contrasting with the closest sibling, pre_trade_check.

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 only implied: a 'safeToTrade verdict' plus 'Informational only, not investment advice' suggests it is a pre-trade gate check. There is no explicit when-to-use/when-not statement and no named alternative (e.g., pre_trade_check, event_study) for the agent to route to.

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