Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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?

No annotations exist, so the description carries the full behavioral burden. It does disclose the response shape (tracked[] with full edge_pp_net time-series, first_seen, trend), which is genuinely useful, but the sentence is cut off mid-word ('trend (') so the response contract is left partially unexplained, and nothing is said about read-only semantics, data staleness, or limits beyond the days cap.

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 sentence and the fresh-vs-aged framing are well front-loaded, but the description terminates mid-sentence, leaving a dangling 'trend (' that visibly truncates the response section. The parenthetical commentary on aged edges is valuable but adds to length in an already incomplete block.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a telemetry/analytics tool with no output schema and no annotations, so the description must fully specify the return contract - and it does not, because the response section is truncated. An agent cannot know the possible trend values, time-series ordering, or what happens when fewer than `days` snapshots exist.

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 constraints. The description restates days (default 14, max 30) and window (snapshot family, default '1wk') without adding semantics the schema lacks, which is the baseline-3 case.

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?

The description names a specific capability - edge persistence and decay telemetry derived from daily polymarket_edges snapshots - and frames it with a concrete question it answers ('how long has this edge existed and is it shrinking?'). Referencing polymarket_edges as the underlying snapshot source distinguishes it from the raw-snapshot sibling.

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?

It gives a clear selection rule: a fresh wide edge and a 3-week-old wide edge are different trades, so use this tool when edge age/maturation matters. It does not explicitly say which sibling to call when age does not matter (e.g. polymarket_edges for a single current snapshot), leaving one routing decision to inference.

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.