Skip to main content
Glama

jikan

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

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

Despite annotations marking it read-only/idempotent, the description adds substantial behavioral detail: snapshots are written only on cache-miss, history is bounded by 60-day TTL, decay is computed on daily closes of edge_pp_net net of default slippage, and missing snapshot dates mean no scan occurred. These limitations are not visible in annotations and significantly shape expected behavior.

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?

The description is long but efficiently organized with labeled sections (Args, RESPONSE, LIMITS). Every sentence adds operational or semantic detail, from the psychological rationale to the TTL limitation, with 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?

For a read-only telemetry tool with no output schema, the description thoroughly documents the response shape (tracked[], expired[], snapshot_dates[]), field meanings, and edge cases. It also explains the data source and limitations, making it fully actionable for an agent.

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 schema already documents both parameters with defaults and ranges. The description adds the 'snapshot family' concept and the max-30 lookback bound, and it explains how parameters affect the response (latest snapshot vs prior snapshots). This is modest added value beyond the 100% schema coverage.

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 states a specific purpose: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots' and answers the question 'how long has this edge existed and is it shrinking?'. This clearly differentiates from sibling polymarket_edges, which likely reports current edges, by focusing on temporal persistence and decay.

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 clear context by framing when edge age matters ('a fresh wide edge and a 3-week-old wide edge are different trades') and what questions it answers. It does not explicitly name alternatives or exclusions, but the purpose strongly implies use for historical edge analysis rather than current edge discovery.

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

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

Many tools serve overlapping purposes (ask_pipeworx, ask_pipeworx_grounded, deep_research, bet_research, compare_entities, entity_profile, recent_changes, validate_claim) all querying Pipeworx data with similar outcomes. An agent would struggle to choose correctly without deep understanding of nuanced differences.

Naming Consistency2/5

Naming conventions are mixed: snake_case (ask_pipeworx, get_anime), camelCase (generate_llms_txt, pipeworx_feedback), and compound names (polymarket_arbitrage, ai_visibility_check). No consistent pattern across the tool set.

Tool Count2/5

34 tools is excessive for a single server. Many are meta-tools (discover_tools, suggest_questions) or narrowly focused (pipeworx_trending, scan_dependency). The server tries to cover too many domains (anime, financial data, predictions, memory) in one surface.

Completeness3/5

The anime tools (search, get, top) form a reasonable read-only surface. The Pipeworx query tools are comprehensive but lack obvious data management tools (e.g., listing sources, managing credentials). Memory tools (remember/recall/forget) are isolated. Overall, gaps exist but core workflows are covered.

Resources