Skip to main content
Glama

Politics Feeds

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?

The description provides extensive behavioral context beyond the annotations: bounded by 60-day TTL, decay from daily closes not intraday, and explains the meaning of expired and snapshot_dates. Annotations (readOnlyHint, openWorldHint, idempotentHint) are consistent and uncontradicted.

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 single paragraph that efficiently conveys key details: purpose, parameter defaults, response structure, and limitations. It is front-loaded with the core question, making it easy to grasp. Could be slightly more structured, but overall concise for the content.

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?

Despite lacking an output schema, the description fully compensates by detailing the response fields (tracked[], expired[], snapshot_dates[]) and their inner structure. It also covers limitations and provenance, ensuring the agent can interpret results correctly.

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%. The description adds defaults (days default 14, max 30; window default '1wk') and clarifies the window family values (24hr, 1wk, 1mo). This adds practical guidance over the schema descriptions.

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's purpose: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers how long has this edge existed and is it shrinking?'. It distinguishes from related tools by focusing on historical persistence rather than current edges, and details the response structure (tracked, expired, snapshot_dates).

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 usage for historical edge analysis but does not explicitly state when to use this tool versus alternatives like polymarket_edges. However, the context of sibling tools and the focus on time-series makes the intended use clear.

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

All Politics Feeds 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

A4/5.0
Disambiguation3/5

Most tools have distinct jobs and the descriptions are unusually explicit about routing, but there are overlapping entry points: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all sit in the same query/research space. ask_pipeworx_beta even states it currently matches ask_pipeworx exactly, which makes some boundaries genuinely ambiguous despite strong descriptions.

Naming Consistency3/5

The set is uniformly snake_case and has useful families like polymarket_* and pipeworx_*, plus many clear verb_noun names (list_feeds, read_feed, resolve_entity, validate_claim). However, roughly a third of tools use noun-led or adjective-led names (entity_profile, deep_research, recent_alerts, polymarket_arbitrage), so the pattern is readable but mixed.

Tool Count2/5

34 tools is far beyond what a 'Politics Feeds' server needs, and a large portion of the surface (npm dependency scanning, AI visibility, memory, prediction markets, LLM text generation) is unrelated to the stated purpose. This feels like a kitchen-sink monolith rather than a scoped feed server.

Completeness4/5

Within its actual implied purpose as a broad Pipeworx data-research platform, the lifecycle is well covered: discover, resolve, ask, ground, research, compare, validate, monitor, subscribe, and remember are all present. The gaps are minor—no update-subscription operation and no direct cross-feed search for the feeds named by the server—so agents can work around them.

Resources