Skip to main content
Glama
Sign In

Gambit

by trading.gambit
OverviewDiscussionsAdmin

Get a ticker's last 1-minute move and gap to its 12-hour EMA

get_gambit_dislocation
Read-onlyIdempotent

One ticker's last 1-minute move and its gap to the 12-hour EMA right now (requires api:read). This is the measure the dislocation check uses to post a market alert and start a news check. symbol: a ticker (reads xyz:, or the main-dex perp such as BTC) or a full xyz: id. Returns perp; category (stock, crypto, fx, rates, commodity or index_etf); bps (the gap ln(close/EMA) in basis points, positive above the EMA, with the EMA over hourly closes); z (that gap over the standard deviation of the hourly gaps across the last week); move_1m_bps and move_1m_x_sd (the last 1-minute return, and its size in hourly sds); threshold_x_sd (the size that fires for this category); would_fire (whether this minute passes every rule: the threshold, the largest minute of the past day, and for stocks at least 2.5% and not in the first minutes after the US open); close, ema and bar_ts (the last bar's close time). 404 not_measurable when the perp has too little history. Gambit runs no model for this call.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesa ticker such as BTC or NVDA, or an exact id such as xyz:GOOGL or ref:eq:IP, as for get_gambit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds meaningful context: api:read permission required, a specific error behavior (404 not_measurable when history is thin), and a clarification that no model runs for this call. It also explains the would_fire rules, though it could be more explicit about rate limits or caching.

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 description is front-loaded with the primary purpose and remains efficient despite its density. The long enumeration of return fields is justified given the absence of an output schema, though the single-paragraph format is less scannable than it could be.

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?

Given a single-parameter, no-output-schema tool with complex real-time semantics, the description covers purpose, token resolution, return fields (bps, z, move_1m_bps, threshold_x_sd, would_fire), error conditions, and auth. An agent has everything needed to call and interpret it correctly.

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%, so the schema already documents the single symbol parameter. The description adds some meaning by explaining that a bare ticker resolves to xyz:<TICKER> or the main-dex perp and that a full xyz: id is also accepted, but this largely overlaps the schema's existing examples, so the baseline of 3 fits.

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: 'One ticker's last 1-minute move and its gap to the 12-hour EMA right now.' It distinguishes the tool from siblings like get_daily_move_context or get_live_snapshot by naming the exact measure and its role in the dislocation check, so an agent can tell what it returns without opening a schema.

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?

The description ties usage to the dislocation check ('the measure the dislocation check uses to post a market alert and start a news check') and states the auth prerequisite (requires api:read). However, it does not explicitly say when-not to use this or name a preferred alternative for related needs such as the 12-hour EMA context or daily move data, leaving the agent to infer from context.

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

All Gambit toolsInspect
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