Skip to main content
Glama

swapi

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).

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond the annotations' read-only/idempotent hints, disclosing critical data caveats: snapshot_dates reveal gaps when nobody scanned, history depth is bounded by a 60-day TTL, decay numbers come from daily closes not intraday, and negative values indicate SELL YES. This transparency about data limitations significantly aids an agent in interpreting results correctly.

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 structured into clear segments: purpose, args, response, and limits, with all information serving a specific purpose. It is slightly longer than absolutely necessary but front-loads the core question and maintains readability with paragraph breaks.

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 thoroughly explains the response structure, including tracked[], expired[], and snapshot_dates[], along with field meanings and interpretation. It also covers historical depth limits and data-generation behavior, making it fully self-contained for an agent using this tool.

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%, so the schema already fully documents both parameters. The description adds the clarifying label 'snapshot family' for window and uses 'lookback' for days, but most parameter semantics (defaults, clamps, enum values) are already in the schema. The added context is minimal but helpful.

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 defines the tool's function as 'edge persistence and decay telemetry built from daily polymarket_edges snapshots' and specifies the core question it answers: 'how long has this edge existed and is it shrinking?' It distinguishes itself from sibling tools like polymarket_edges by focusing on historical persistence rather than current snapshots, making it a unique resource.

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 provides strong contextual guidance, explaining that the tool serves to differentiate fresh from old edges and warning that a 3-week-old wide edge 'is wide for a reason nobody is willing to take.' However, it doesn't explicitly name alternatives or state when not to use it, so the usage guideline is implicit rather than explicit.

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

All swapi 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
Disambiguation3/5

The tool set mixes two unrelated domains (Star Wars and Pipeworx data services), which is initially confusing. Within the Pipeworx suite, tools like ask_pipeworx and ask_pipeworx_grounded are clearly differentiated, but some overlap exists (e.g., deep_research vs. compare_entities both do multi-source lookups). Overall, most tools have distinct purposes, but the domain mismatch lowers clarity.

Naming Consistency4/5

All tools use snake_case consistently (e.g., ask_pipeworx, entity_profile, resolve_entity). The naming pattern is mostly verb_noun or descriptive_compound, which is predictable. Minor deviation: some tools start with a verb (ask_pipeworx) while others start with a noun (entity_profile), but the style is uniform.

Tool Count3/5

34 tools is on the high side but not unreasonable for a data-heavy server. However, the set covers two distinct domains (Star Wars and Pipeworx), making it feel bloated. The count could be reduced by separating the domains or pruning rarely-used tools.

Completeness3/5

The Pipeworx side appears comprehensive, covering queries, profiles, comparisons, subscriptions, alerts, and memory. The Star Wars side is incomplete—it lacks tools for vehicles, species, or individual characters (only search_people exists). The overall surface has gaps in one of its two domains.

Resources