Skip to main content
Glama

Currencyformat

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 read-only, open-world, idempotent, and non-destructive. The description adds significant detail: response structure (tracked, expired, snapshot_dates), field meanings, and limitations (60-day TTL, cache-miss gaps). 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 detailed and front-loaded with main purpose. Every sentence adds value, though it is somewhat dense and could be slightly more structured. Nonetheless, it avoids waste and is efficient for 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?

Given no output schema, the description fully explains the return structure: tracked with time-series, first_seen, trend, decay_pp_per_day; expired with lifespan_days; snapshot_dates and gaps. It also covers limits (60-day TTL, cache-miss behavior). The description is complete for the tool's complexity.

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?

The input schema already describes both parameters with 100% coverage. The description adds context such as default values, clamping for days, and snapshot family explanation, as well as behavior around cache-miss gaps, which enriches parameter understanding beyond the schema.

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 clearly states the tool provides 'edge persistence and decay telemetry' and answers a specific question about edge duration. It distinguishes itself from sibling polymarket_edges by focusing on historical time-series and trend analysis rather than current edges.

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 gives clear context on when to use this tool (to assess if an edge is decaying) with the example of fresh vs. old wide edges. However, it does not explicitly state when not to use it or mention alternatives beyond implying polymarket_edges for fresh data.

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

All Currencyformat 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.7/5.0
Disambiguation2/5

Multiple tool clusters have overlapping functions: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly interchangeable, deep_research overlaps with the ask_pipeworx family, and the six Polymarket tools all analyze the same domain with subtle differences. discover_tools and suggest_questions also both serve as discovery entry points, making it difficult for an agent to confidently select the correct tool.

Naming Consistency3/5

All names are snake_case, but there is no uniform structural pattern. Verb_object names like format_currency and resolve_entity coexist with noun_phrases like entity_profile and polymarket_arbitrage, bare verbs like remember and forget, and adjective_noun forms like recent_alerts. Cluster-specific prefixes are consistent, but the overall convention is mixed.

Tool Count2/5

With 33 tools, the set is substantially over-scoped and exceeds the suggested 3-15 range. Many tools could be consolidated, such as the three ask_pipeworx variants, the six Polymarket tools, and the two formatting utilities. The broad domain justifies some size, but the count feels inflated and will burden agents with excessive choice.

Completeness3/5

The server covers many areas thoroughly: memory has remember/recall/forget, subscriptions have subscribe/unsubscribe/list/recent_alerts, and research tools span lookup, profiling, comparison, and verification. However, there are notable gaps: pipeworx:// citation URIs are returned but no tool explicitly fetches or reads a record by URI, and there is no direct way to manage account-level settings beyond memory. These missing operations force agents to work around limitations.

Resources