Skip to main content
Glama

Tradier

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?

Adds extensive behavioral context beyond annotations: explains data source (daily snapshots), return structure (tracked, expired, snapshot_dates), decay computation methodology, and limitations (not intraday). Annotations already indicate read-only, but description enriches understanding.

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?

Relatively dense but each sentence adds unique value. Could be slightly more concise (e.g., avoid repeating 'snapshots' multiple times), but front-loads purpose and key concepts effectively.

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 all return fields (tracked, expired, snapshot_dates) and their subfields (trend, decay, lifespan). Also covers limits and data source details. Highly complete for a tool with two optional parameters.

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 covers 100% of parameters, but description adds value: specifies default and clamp range for 'days' and default value for 'window', plus notes about response fields that depend on parameters. Justifies a 4.

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?

Clearly states the tool provides 'edge persistence and decay telemetry' from daily snapshots, answering a specific trading question about edge age and decay. Distinguishes from sibling 'polymarket_edges' by focusing on time-series analysis.

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?

Explicitly describes when to use (e.g., comparing fresh vs. old wide edges) and mentions limits like 60-day TTL. Does not explicitly state when not to use or name alternatives beyond the context.

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

All Tradier 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 tools share overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants, and the five polymarket_* tools cover heavily overlapping territory. An agent must read lengthy descriptions to distinguish between them, and pairs like validate_claim vs ask_pipeworx_grounded or discover_tools vs suggest_questions have fuzzy boundaries.

Naming Consistency2/5

Naming is wildly inconsistent: verb_noun (compare_entities, discover_tools), bare verbs (forget, remember, subscribe), noun phrases (entity_profile, recent_alerts, pipeworx_feedback), prefixed families (tradier_*, polymarket_*) and suffixed variants (ask_pipeworx_beta, ask_pipeworx_grounded). There is no single predictable convention across the set.

Tool Count2/5

34 tools is far beyond the 15-25 heavy range, and the count is inflated by near-duplicates like ask_pipeworx/ask_pipeworx_beta and five polymarket edge tools. The server mixes several unrelated domains (Tradier quotes/options, Pipeworx research, Polymarket analysis, memory, subscriptions, web utilities), making the scope feel unbounded.

Completeness2/5

For a server named Tradier, having only quote and option-chain endpoints is a significant gap—no historical data, account, positions, or order execution. The Pipeworx/Polymarket side is more complete, but the inclusion of unrelated utilities like generate_llms_txt and scan_dependency means no single domain is fully served.

Resources