Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavioral traits: the data source (daily snapshots), the lookback cap (max 30), and the response structure (tracked[] with edge_pp_net time-series, first_seen, trend). It never states the operation is read-only or what happens when the snapshot history is shorter than the requested lookback. That is a moderate gap but the disclosure of data provenance and return shape is well above minimal.

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 opening is well front-loaded: purpose, then the interpretive insight, then args, then response. However, the final RESPONSE sentence is truncated mid-phrase ('trend ('), leaving a dangling fragment that wastes the most information-dense position in the description. The middle 'fresh wide edge vs 3-week-old edge' aside is valuable but slightly verbose.

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 return values and it attempts to via tracked[] / first_seen / trend — but the sentence is cut off exactly where the field semantics would be defined. Combined with the absence of any read-only or history-availability note, an agent still has unresolved questions about what 'trend' contains and what happens if fewer than `days` snapshots exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines both parameters; the baseline is 3. The description adds meaning beyond the schema by explaining default 14/max 30 and by clarifying that 'window' selects the snapshot family rather than a display grouping. Marginal but genuine value added on top of a fully documented 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?

The description names a specific resource and analytical angle: edge persistence and decay telemetry derived from daily polymarket_edges snapshots, framed as 'how long has this edge existed and is it shrinking?'. The contrast between a fresh wide edge and a 3-week-old wide edge makes the tool's distinct value obvious. It does not explicitly name the sibling snapshot tool (polymarket_edges) as the alternative, so sibling differentiation is conceptual rather than explicit.

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 through the framing question about edge age and decay, and through the 'fresh vs old edge' observation, which tells an agent when this matters. There is no explicit when-not-to-use or a named alternative for raw/latest-snapshot data, so the agent must infer that polymarket_edges covers the single-snapshot case.

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.