Skip to main content
Glama

Mychem

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

TDQS

A4.3/5.0
Behavior5/5

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

Discloses behavioral traits beyond annotations: snapshot TTL (60-day), data gaps due to cache-miss, and detailed response structure. Annotations already indicate safe read-only, but description adds critical context about data freshness and limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is informative but verbose with long sentences. Front-loaded with purpose, but could be more concise. Well-structured with sections but some redundancy.

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 no output schema, the description fully explains the return format (tracked, expired, snapshot_dates) and edge cases (gaps, TTL). Covers all necessary context for a complex tool.

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?

Schema coverage is 100% with detailed descriptions. The description adds minor context (e.g., default/max values) but does not significantly enhance understanding beyond the schema.

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: answering 'how long has this edge existed and is it shrinking?' and distinguishes it from sibling tools like polymarket_edges by focusing on persistence telemetry. Uses specific verb+resource structure.

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?

Provides clear context on when to use: to differentiate between fresh and old edges. While it doesn't explicitly list exclusion cases, the context about edge aging implies usage scenarios.

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

All Mychem 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
Disambiguation2/5

The set contains several near-duplicate entry points (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) plus a dense family of polymarket_* and chemical lookup tools whose boundaries are subtle. An agent can easily pick the wrong router variant, edge-scanning tool, or chemical search tool.

Naming Consistency3/5

Snake_case is used throughout, but naming style is mixed: some tools are verb-first (query, resolve_entity, validate_claim), some are noun/domain-first (entity_profile, recent_changes, polymarket_arbitrage), and the ask_pipeworx variants use suffixes instead of a consistent verb pattern. It is readable, but there is no predictable convention beyond snake_case.

Tool Count2/5

34 tools is well past the comfortable range, and the count is especially hard to justify because they span unrelated domains: chemistry lookups, a Pipeworx data gateway, prediction-market analytics, memory, subscriptions, AI-visibility checks, and npm dependency scanning. Many of these have no obvious connection to the 'Mychem' name or to each other.

Completeness4/5

Within each contained workflow the surface is fairly complete: chemistry has search/fetch/metadata, Pipeworx has lookup/research/discovery/validation, subscriptions and memory both have lifecycle coverage, and the Polymarket family covers research, edge detection, persistence, and fill risk. Some minor gaps exist (no general web retrieval or execution/trading action), but agents can work around them.

Resources