Skip to main content
Glama

Arcgis Charlotte

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

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

Annotations already declare readOnly and idempotent hints. The description adds significant behavioral details: history is bounded by a 60-day snapshot TTL, decay is computed from daily closes (not intraday), and snapshot gaps indicate days with no scans. This goes well beyond what annotations provide.

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 long but well-organized with 'Args:', 'RESPONSE:', and 'LIMITS:' sections. The first sentence conveys purpose immediately. Each sentence carries information, though it could be tighter. It earns its length.

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?

With no output schema, the description fully explains the response structure (tracked[], expired[], snapshot_dates[]) and includes limits. It covers data semantics, edge cases (gaps), and historical depth, making it self-sufficient for an agent to use correctly.

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 descriptions for both days and window. The description repeats defaults (14, 1wk) and adds 'max 30' which is already in the schema as clamp 2-30. No new parameter meaning is added, so baseline 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 states the tool's purpose: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots' and explicitly answers 'how long has this edge existed and is it shrinking?' It differentiates from siblings like polymarket_edges by focusing on time-series persistence and decay.

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 usage context: when you need to distinguish a fresh wide edge from an old one ('a fresh wide edge and a 3-week-old wide edge are different trades'). It does not explicitly name alternative tools, but the context implies when this telemetry is relevant. No exclusions are stated.

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

All Arcgis Charlotte 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.8/5.0
Disambiguation2/5

Several tools are easy to confuse: ask_pipeworx_beta is currently identical to ask_pipeworx, deep_research overlaps heavily with ask_pipeworx/ask_pipeworx_grounded, and the six polymarket_* tools have closely related purposes. ai_visibility_check and scan_competitor_ai_presence also overlap, making selection error-prone.

Naming Consistency4/5

Almost all tools use lowercase snake_case and mostly follow a verb_noun pattern (query_layer, resolve_entity, scan_dependency, validate_claim). A few noun-style names like entity_profile, layer_info, and pipeworx_trending deviate slightly, but the overall convention is predictable.

Tool Count2/5

34 tools is well past the heavy threshold, and the server is named 'Arcgis Charlotte' while only three tools actually relate to ArcGIS. The rest form a sprawling Pipeworx research, prediction-market, subscription, and memory toolkit, which creates a severe scope mismatch.

Completeness2/5

For the Pipeworx data side the surface is quite thorough, but for the declared ArcGIS Charlotte purpose it is thin: search_datasets, layer_info, and query_layer provide read-only access with no update/delete, analysis, or dataset management. The tool set therefore has a significant gap relative to its stated domain.

Resources