Skip to main content
Glama

Destatis

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. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds significant context: it explains that snapshots have gaps ('gaps mean nobody scanned that day'), describes the derived trend/decay calculations, and clarifies that decay numbers come from daily closes. No contradiction with annotations.

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?

The description is a dense paragraph but contains no filler; every sentence adds value. It is front-loaded with the core purpose and then details output structure and limits. Could benefit from more structured formatting, but it's concise given the complexity.

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?

With no output schema, the description fully covers the return structure: tracked[], expired[], snapshot_dates[], and explains derived fields (first_seen, trend, decay_pp_per_day). Also addresses data gaps and TTL limits, making it complete for effective tool usage.

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% for both parameters. The description adds practical context: default for days is 14 with max 30, default window is '1wk', and explains the snapshot family concept. It enhances understanding without being necessary for correctness.

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 provides a specific verb+resource combination: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots.' It clearly distinguishes itself from sibling tools like polymarket_edges by focusing on historical persistence and decay, answering 'how long has this edge existed and is it shrinking?'

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 implicitly guides usage by contrasting fresh vs. old wide edges, and mentions LIMITS like the 60-day snapshot TTL. However, it does not explicitly state when not to use this tool or name direct alternatives, so it does not achieve a 5.

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

All Destatis 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

A3.9/5.0
Disambiguation2/5

The ask_pipeworx family—ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded—plus deep_research all describe the same router under slightly different modes, and the six polymarket tools overlap heavily around edge detection and arbitrage. ai_visibility_check and scan_competitor_ai_presence are also near-duplicates, so agents will frequently have to choose between tools that appear to do the same thing.

Naming Consistency3/5

All names use snake_case and several families share prefixes (ask_pipeworx, polymarket_, pipeworx_, destatis_), which helps discoverability. However the pattern is not consistent: bare verbs (remember, recall, forget), adjective_noun phrases (recent_alerts, recent_changes), and noun_noun names (entity_profile, bet_research) are all mixed.

Tool Count2/5

With 33 tools, the surface is well past the 25+ threshold and mixes unrelated concerns: Destatis statistics, a general data router, prediction-market analytics, memory, and AI-marketing scans. The count could be justified if split into separate servers, but as one set it feels over-stuffed.

Completeness4/5

For the broad data-retrieval/research purpose the descriptions reveal, coverage is strong: lookup, grounded answers, validation, entity resolution, comparison, change feeds, subscriptions, memory, and Destatis search/table are all present. The only notable weakness is that the Destatis-specific surface is just search-and-fetch, which is thin for a server literally named Destatis, but this is offset by the general router.

Resources