Skip to main content
Glama

Washington State Open Data

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

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

Annotations indicate readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds significant behavioral context: explains the snapshot-based data source, return structure (tracked, expired, snapshot_dates), limitations (60-day TTL, daily closes), and caveats (decay from daily closes not intraday). This far exceeds the annotation baseline.

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 and example. It includes necessary details about response format and limitations without excessive verbosity. However, it could be slightly more concise by moving some details to a separate notes section.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of decay telemetry and the lack of an output schema, the description adequately explains the return structure (tracked, expired, snapshot_dates) and key nuances (trend, decay_pp_per_day, lifespan). It also mentions caching and snapshot gaps. It is complete for an experienced user but might benefit from brief examples.

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%; both parameters (days, window) are fully described in the schema. The description restates defaults and adds the response structure, which is helpful for understanding output but does not significantly enhance parameter semantics 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: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots.' It explains what the tool answers and distinguishes it from sibling tools like polymarket_edges by focusing on persistence/decay rather than raw edges.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context on when to use the tool (e.g., evaluating fresh vs. old edges) but does not explicitly state when to use this tool over alternatives like polymarket_edges or polymarket_arbitrage. It gives default parameters and limits but lacks clear guidance on exclusion.

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

All Washington State Open Data 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.6/5.0
Disambiguation4/5

Most tools have distinct purposes with detailed descriptions, but there is overlap between ask_pipeworx, ask_pipeworx_grounded, and deep_research, all serving data retrieval. Also, prediction market tools (e.g., bet_research, polymarket_arbitrage) are closely related, causing potential ambiguity.

Naming Consistency2/5

Naming conventions are inconsistent: mostly snake_case (ask_pipeworx, entity_profile) but includes camelCase (ai_visibility_check). No clear pattern, mixing verb_noun and other structures.

Tool Count1/5

33 tools is excessive for a server named 'Washington State Open Data'; only 3 tools (datasets, metadata, query) are directly relevant, while the rest are unrelated Pipeworx/Polymarket tools. The count does not match the server's stated scope.

Completeness1/5

The tool set severely misaligns with the server name: it covers general data and prediction markets rather than Washington State Open Data. Only basic query and metadata tools exist for the stated domain, leaving many common dataset operations (e.g., CRUD) missing and providing entirely irrelevant functionality.

Resources