Skip to main content
Glama

Pkg Go Dev

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

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false. The description adds significant behavioral context beyond annotations: it explains data bounded by 60-day snapshot TTL, snapshots only on cache-miss (gaps mean no scan), decay from daily closes not intraday, and output structure including trend computation. No contradictions with 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 front-loaded with the core purpose, followed by args and response structure, then limitations. It is moderately long but every sentence adds value. Minor redundancy could be trimmed (e.g., 'daily polymarket_edges snapshots' repeated). Overall well-organized for the complexity of the tool.

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 having no output schema, the description thoroughly details the response structure: tracked array with full time-series, first_seen, trend, decay_pp_per_day; expired array with lifespan_days; snapshot_dates. It also covers limits (60-day TTL, snapshot start time, intraday vs daily). This provides complete context for agent usage.

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 both parameters (days, window) with descriptions. The description adds value by specifying default values (14 days, '1wk'), clamping behavior (max 30), and enumerating snapshot families ('24hr', '1wk', '1mo') which are not listed in the schema. This provides concrete options beyond schema documentation.

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: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots,' answering 'how long has this edge existed and is it shrinking?' It distinguishes itself from sibling tools like polymarket_edges by focusing on time-series telemetry rather than current edges. The verb and resource are specific and non-tautological.

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 usage context by explaining that a fresh wide edge and a 3-week-old wide edge are different trades. It implies when to use this tool (to assess edge persistence) but does not explicitly name alternative tools or state when not to use it. The guidance is clear but could be more definitive with exclusion criteria.

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

All Pkg Go Dev 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

B3.4/5.0
Disambiguation2/5

Multiple tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded all performing similar data lookups. Additionally, many tools focus on prediction markets and arbitrage, which are unrelated to the server's implied Go development domain, causing confusion.

Naming Consistency2/5

Tool names follow inconsistent conventions: some use snake_case (e.g., 'latest_version', 'list_versions'), some use underscores in longer names (e.g., 'ai_visibility_check', 'ask_pipeworx_grounded'), and some use colons in descriptions but not in names. This mix reduces predictability.

Tool Count2/5

With 35 tools, the count is high for a server named 'Pkg Go Dev' that only offers a few Go module-related tools (e.g., get_go_mod, list_versions). The majority are unrelated Pipeworx tools, making the scope mismatched and excessive.

Completeness1/5

The tool set severely lacks coverage for Go development tasks. It only includes basic module lookup tools (version listing, mod retrieval) but misses essential operations like dependency analysis, build commands, or testing. The vast majority of tools cover unrelated domains (prediction markets, company profiles, etc.), leaving the server incomplete for its intended purpose.

Resources