Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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 supplied, the description carries the full behavioral burden, and it does add real context: the data is derived from daily snapshots, tracked[] is anchored to the LATEST snapshot cohort, and each entry carries a historical time-series plus first_seen and trend. However, the response section is cut off mid-sentence ('trend ('), so the agent never learns the complete return shape or any caveats about missing history for newly appearing markets.

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 lead sentence and the trading-rationale sentence are front-loaded and earn their place, but the description is visibly truncated at 'trend (' — an incomplete sentence that leaves the structure broken. The parenthetical aside about why an old wide edge is wide is colorful but longer than needed for an agent-facing definition.

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?

The tool has no output schema and no annotations, so the description must fully explain the return shape, and it only gets partway before being cut off. It does establish the key structural facts (tracked[] cohort from the latest snapshot, time-series, first_seen, trend), which is more than nothing, but the truncated tail leaves the response contract materially incomplete.

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 parameters are already fully documented in the schema, making 3 the correct baseline. The description restates days and window with their defaults and adds a slight framing difference ('max 30') versus the schema's 'clamp 2-30', which is not an explanation the schema lacks. It adds no new meaning such as how days interacts with window granularity.

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?

Opens with a specific framing: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots,' which distinguishes it from the raw polymarket_edges sibling by making clear this is a derived, longitudinal view rather than a snapshot listing. The quoted question ('how long has this edge existed and is it shrinking?') makes the intent concrete. It falls short of 5 only because it never names polymarket_edges explicitly as the alternative to use for a single-day view.

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 conveyed by implication through the trading rationale — 'a fresh wide edge and a 3-week-old wide edge are different trades' — which tells the agent this tool is for persistence/aging analysis rather than discovery. There is no explicit when-to-use/when-not-to-use statement and no named alternative among the siblings (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk). The agent must infer the routing decision.

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.