Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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

A3.6/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 useful traits: data comes from daily snapshots, output is anchored to the LATEST snapshot, and lookback is capped. However, the response section is truncated mid-sentence at 'trend (', so the behavior of the most important output field is left undefined, and nothing is said about latency, rate limits, or what happens when no prior snapshots exist.

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 description is front-loaded and the conceptual framing earns its place, but the Args and RESPONSE sections duplicate the schema, and the text terminates mid-sentence at 'trend (', which is a real structural defect rather than brevity.

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?

For a two-optional-parameter read tool with no output schema, the description supplies the data provenance, the anchoring rule, and a partial return-value map, which is close to sufficient. The truncation of the tracked[] field list leaves the return contract incomplete at the point an agent most needs it.

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 coverage is 100%, so both parameters are already documented, and the description largely restates them. It adds only marginal value by calling window a 'snapshot family', and it introduces a small discrepancy with the schema by saying 'max 30' where the schema says 'clamp 2-30'.

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 opening states a specific resource and verb: edge persistence and decay telemetry derived from daily polymarket_edges snapshots, framed by the question it answers. That distinguishes it from the plain polymarket_edges snapshot sibling by making clear it is a time-series overlay rather than a raw listing, though it never names the sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'fresh wide edge vs 3-week-old wide edge' framing gives a concrete decision rule for when this tool is the right call over a single-snapshot view. It stops short of stating exclusions or naming the alternative tool to use for one-off opportunity listings.

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.