Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__polymarket_edge_tracker

Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?", a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: days (lookback, default 14, max 30), window (snapshot family, default "1wk"). RESPONSE: tracked[] = every opportunity in the LATEST snapshot with its full edge_pp_net time-series across prior snapshots, first_seen, trend (

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "days": 14,
      "window": "1wk"
    },
    "name": "ntsb-investigations__polymarket_edge_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLookback in days (default 14, clamp 2-30).
windowNoWhich polymarket_edges window family to read snapshots for: 24hr | 1wk | 1mo (default 1wk).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: it reads daily snapshots, defaults days to 14 with a max of 30, and returns tracked[] entries keyed to the LATEST snapshot with full prior time-series, first_seen and trend. However, it omits read-only/cost characteristics, what happens when history is shorter than the lookback, and the text is cut off mid-sentence, so the disclosure is partial.

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 dense and mostly front-loaded, and the parenthetical about 'wide for a reason nobody is willing to take' earns its place by conveying intent. But the description terminates mid-token ('trend ('), leaving the response contract visibly unfinished and undermining structure.

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 must explain the return value, and it does begin to (tracked[] with edge_pp_net time-series, first_seen, trend) — but it is truncated before completing that list, leaving the most important part of the contract incomplete for a tool whose whole value is the returned series.

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 both params are already documented in the schema; the description restates the days default and adds the framing of window as a 'snapshot family'. That is marginal added meaning, and it actually introduces a soft inconsistency (description says 'max 30' while the schema says clamp 2-30). 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?

The description states a specific analytical purpose — edge persistence and decay telemetry built from daily snapshots — and frames it as answering 'how long has this edge existed and is it shrinking?'. It also clarifies the relationship to the polymarket_edges snapshots it reads, though it never explicitly contrasts itself with the polymarket_edges sibling as an alternative for current-only data. An agent can tell what this returns but not precisely which sibling to pick instead for the plain snapshot case.

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 'fresh wide edge vs 3-week-old wide edge' framing tells the agent this is for judging edge durability, but there is no explicit when-to-use/when-not-to-use rule and no named alternative (e.g., polymarket_edges) for cases where persistence isn't needed. Adequate context, no exclusions.

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.