Skip to main content
Glama

Arcgis Fairfield

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

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

Beyond the readOnly/idempotent annotations, the description details the response structure (tracked[], expired[], snapshot_dates[]), limitations (60-day TTL, snapshot gaps from cache-miss), and calculation methodology (decay from daily closes, absolute value convention). This far exceeds the annotations and provides critical operational context.

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?

The description is dense but well-organized, starting with the core question, then covering parameters, response fields, and limitations in a logical sequence. Each sentence adds necessary value—there is no fluff or redundancy—making it appropriately sized for the tool's complexity.

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 absence of an output schema, the description fully specifies the response fields and their semantics, including trend values, decay calculation, expiry reasons, and snapshot date gaps. It also covers history depth and data caveats, making it complete for a complex telemetry 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?

The input schema already covers both parameters completely (days with default and clamp range, window with allowed values). The description restates the defaults and adds 'snapshot family' terminology but does not provide any additional meaning beyond the schema. With 100% schema coverage, the baseline score of 3 is appropriate.

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 identifies the tool as 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots' and answers a specific question about edge age and shrinkage. This distinguishes it from sibling tools like polymarket_edges by focusing on historical time-series rather than current edge values.

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 ('Answers how long has this edge existed and is it shrinking?') and uses an example to illustrate trade relevance. However, it does not explicitly name alternative tools or state when not to use it, falling just short of a full 5.

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

All Arcgis Fairfield 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, such as ask_pipeworx, ask_pipeworx_grounded, deep_research, and also multiple Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage). Descriptions try to differentiate but the boundaries are unclear, causing confusion.

Naming Consistency2/5

Naming conventions are mixed: some use snake_case (ask_pipeworx, query_layer), some use descriptive phrases (entity_profile, recent_changes), and there is no consistent verb_noun pattern. The variety makes it hard to predict tool names.

Tool Count1/5

33 tools is far too many for a server named 'Arcgis Fairfield', as most tools are unrelated to GIS or Fairfield (e.g., npm dependency checks, prediction markets, AI visibility). The tool count severely mismatches the server's purported scope.

Completeness1/5

The server's stated purpose is ArcGIS Fairfield, but only 3 tools (layer_info, query_layer, search_datasets) relate to that domain. Critical GIS operations like updating features or managing services are missing, while the vast majority of tools are for other domains.

Resources