Skip to main content
Glama

wikifeed

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.4/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds significant behavioral context: snapshots are written on cache-miss so gaps mean no scan, history is bounded by a 60-day TTL, and decay is computed from daily closes rather than intraday. This goes far beyond the 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 verbose but well-structured with labeled sections (Args, RESPONSE, LIMITS). It earns most of its length given the tool's complexity, though some elaborative phrases could be trimmed without losing value.

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 explains the response shape (tracked, expired, snapshot_dates), the meaning of edge values (negative = SELL YES), and all relevant limitations. It covers every aspect an agent would need to use the tool 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?

The input schema already provides 100% coverage with descriptions and clamps for both parameters. The description restates defaults and adds the 'snapshot family' concept, but this is marginal reinforcement rather than substantial new meaning.

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 explicitly identifies the tool as 'edge persistence and decay telemetry' and states the exact question it answers ('how long has this edge existed and is it shrinking?'). This distinguishes it clearly from siblings like polymarket_edges, which focus on current edge data.

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 provides a strong contextual use case by contrasting fresh vs. old edges and implying when to use it (when edge age/decay matters). However, it does not explicitly name alternative tools or state when not to use it (e.g., for current edges, use polymarket_edges).

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

All wikifeed 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
Disambiguation4/5

Most tools have clearly distinct purposes, but some overlap exists: ask_pipeworx and ask_pipeworx_grounded are very similar (one grounded), and multiple Polymarket tools (arbitrage, edges, tracker, fill_risk, kalshi_spread) could be confused despite distinct roles. Overall, an agent can usually differentiate with careful reading.

Naming Consistency3/5

Tool names follow mixed conventions: some use verb_noun (ask_pipeworx, compare_entities), others start with prefixes (pipeworx_, polymarket_, scan_), and a few are nouns (most_read, on_this_day). While readable, there is no consistent pattern, making it harder to predict tool names.

Tool Count3/5

34 tools is high but not extreme for a broad-scope server. However, the server name 'wikifeed' suggests a Wikipedia focus, yet only 4 of 34 tools relate to Wikipedia (featured_article, most_read, on_this_day, picture_of_day). The tool count feels excessive relative to the name, but the actual breadth may justify it.

Completeness4/5

The toolset covers a wide range of domains (company data, prediction markets, factual queries, Wikipedia) with reasonable depth. Minor gaps exist: no Wikipedia search or edit tools, no direct tool for simple web search (relying on ask_pipeworx). Overall, agents can accomplish most tasks without hitting dead ends.

Resources