Skip to main content
Glama

timezone

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

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

Beyond the readOnlyHint and other annotations, the description discloses extensive behavioral details: decay is computed on |edge_pp_net| using daily closes, value sign indicates trade direction, history is bounded by a 60-day TTL, snapshot gaps signify no scan, and expired opportunities represent closed/resolved/arbed-away events. These limitations and semantics materially help an agent interpret 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?

Although lengthy, the description is tightly structured: purpose, use-case analogy, arguments, detailed response fields, and limits. Every sentence carries unique information—no filler or redundancy. The front-loaded purpose and response schema analogue make it easy to scan.

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 the complexity of telemetry across time-series snapshots and the lack of an output schema, the description is exceptionally complete. It explains all response components (tracked[], expired[], snapshot_dates[]), the meaning of trend/decay, the impact of TTL and gaps, and the source of snapshots. An agent can confidently invoke the tool and interpret results without further clarification.

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 description coverage is 100% for both parameters, so the schema already fully documents days and window. The description adds minor context by calling window a "snapshot family" and restating defaults, but it does not introduce new syntactic or semantic details 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 opens with a specific verb and resource: "Edge persistence and decay telemetry built from daily polymarket_edges snapshots," and immediately frames the question it answers: "how long has this edge existed and is it shrinking?" This clearly distinguishes it from the sibling polymarket_edges tool, which likely shows current edges, by focusing on temporal history and trend.

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 clear context for when to use the tool: when edge age and decay matter, as in "a fresh wide edge and a 3-week-old wide edge are different trades." It also explains how snapshots are produced and what gaps mean. However, it does not explicitly name alternatives or state when NOT to use this tool, leaving the comparative guidance implicit.

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

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

Many tools have overlapping purposes, especially the multiple 'ask_pipeworx' variants and several Polymarket utilities. The server mixes a few timezone tools with a large collection of unrelated data lookup and analysis tools, making it hard for an agent to distinguish which tool to use for a given task.

Naming Consistency2/5

While all tool names use snake_case, the verbs are highly inconsistent (e.g., 'ask_pipeworx', 'convert_time', 'discover_tools', 'validate_claim'). There is no clear pattern or predictable naming convention across the set.

Tool Count2/5

The server name 'timezone' suggests a narrow domain, but it contains 35 tools, the vast majority of which are unrelated to timezones. This is far too many for the implied scope, and the server seems to be a dumping ground for various services.

Completeness1/5

For a timezone server, only 4 tools (convert_time, get_time_by_ip, get_time_by_timezone, list_timezones) are relevant. Critical timezone functionality like time zone conversions with arbitrary offsets, DST handling, or time zone by coordinates is missing. The remaining tools are completely unrelated to the server's stated purpose.

Resources