Skip to main content
Glama

postcodes

by io.github.pipeworx-io

Polymarket Edge Tracker

polymarket_edge_tracker
Read-onlyIdempotent

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 (new | widening | stable | decaying) and decay_pp_per_day (both computed on |edge_pp_net| — the value itself is signed by trade direction, negative = SELL YES); expired[] = opportunities that appeared in earlier snapshots but are GONE from the latest (closed, resolved, or arbed away) with their lifespan_days — the median lifespan is your competition clock; snapshot_dates[] = which days actually have data (snapshots are written when polymarket_edges runs on a cache-miss, so gaps mean nobody scanned that day). LIMITS: history depth is bounded by the 60-day snapshot TTL and starts from when snapshotting was enabled; decay numbers come from daily closes of edge_pp_net (net of default slippage), not intraday.

Input Schema

TableJSON 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. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already indicate readOnly, openWorld, idempotent, and non-destructive behavior. The description goes far beyond this by explaining the response structure (tracked, expired, snapshot_dates), limitations (60-day TTL, snapshot gaps), and interpretation details (decay based on daily closes, signed edge values). This provides rich behavioral context with no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is long but well-structured with clear divisions (Args:, RESPONSE:, LIMITS:). It front-loads the core purpose, then details parameters and output, ending with limitations. Every sentence adds substantive information; no filler.

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

Completeness5/5

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

Given the tool's moderate complexity and absence of an output schema, the description fully compensates by detailing the response objects (tracked, expired, snapshot_dates) and their fields, plus important caveats. The agent has enough information to invoke the tool and interpret results correctly.

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 covers 100% of parameters (days, window) with clear descriptions. The description adds minor context like 'snapshot family' and echoes defaults but doesn't significantly improve on the schema. It omits the min clamp for days (2) that the schema includes. Baseline 3 is appropriate.

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?

Description clearly states the tool's unique function: edge persistence and decay telemetry. It answer a specific trading question (how long has an edge existed and is it shrinking?) and distinguishes itself from sibling tools like polymarket_edges by focusing on historical snapshots. The verb 'answers' gives a concrete use case.

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 description implies when to use this tool: when you need to understand edge persistence over time, not just current edges. It mentions being built from daily polymarket_edges snapshots, which suggests it complements the sibling polymarket_edges tool. However, it doesn't explicitly name alternatives or state when not to use it, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All postcodes toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Many tools have overlapping responsibilities: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded all serve similar lookup purposes. entity_profile, compare_entities, and recent_changes all retrieve company data. Several Polymarket tools overlap in edge detection. The large number of tools with fuzzy boundaries makes it difficult for an agent to select the correct one.

Naming Consistency3/5

Tool names are a mix of conventions: some use verb_noun (lookup_postcode, validate_postcode, resolve_entity), others are verb_phrase (ask_pipeworx, deep_research, suggest_questions), and a few are compound (polymarket_arbitrage, scan_competitor_ai_presence). No uniform pattern, though the structure is readable.

Tool Count1/5

Despite being named 'postcodes', only 4 of 35 tools are directly about postcodes. The vast majority belong to a broad data platform (Pipeworx) with specialized tools for finance, betting, news, etc. The count is excessive for a focused service, and many tools are only useful for users of that platform, leading to clutter.

Completeness2/5

For a postcode server, the tools cover basic needs (lookup, nearest, random, validate). However, the server's actual scope is much larger; within that broader scope, there are notable gaps: no general text search, no direct access to raw SEC filings, and many tools depend on paid plans or external accounts. The coverage is uneven and incomplete for a unified data platform.

Resources