Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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

A4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does substantial work: it discloses the underlying data source (daily polymarket_edges snapshots), the lookback ceiling (max 30 days), and the shape of the response (tracked[], edge_pp_net time-series, first_seen, trend). The disclosure is cut off mid-sentence at 'trend (', leaving the return contract and any staleness/cadence caveats unfinished.

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?

Dense and front-loaded: purpose, motivation, arguments, and response are ordered well and no sentence is filler. The value proposition sentence about fresh vs. old wide edges earns its place, though the trailing 'trend (' fragment leaves the structure visibly unfinished.

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?

With only two optional parameters and no output schema, the description is nearly sufficient, but the response explanation — the one thing structured fields cannot supply here — is truncated after 'trend (', so an agent cannot learn the full trend encoding or remaining returned fields. Enough is present to call it correctly, not enough to interpret results confidently.

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 with defaults and allowed values. The description restates the same defaults and adds only a 'max 30' note, omitting the schema's lower clamp of 2, so it neither conflicts meaningfully nor adds interpretation of what 'window' means analytically. Baseline 3 applies when the schema does the heavy lifting.

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 capability with a verb-and-resource framing: edge persistence and decay telemetry derived from daily snapshots. The quoted question 'how long has this edge existed and is it shrinking?' plus the fresh-vs-3-week-old example makes the tool's job unmistakable to an agent.

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?

Gives clear usage context by framing the decision it supports (is a wide edge stale or genuine?) and warns that a fresh wide edge and an old wide edge are different trades. It stops short of explicit exclusions or naming an alternative tool for raw current edges, so it is clear context without full when-not guidance.

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.