Skip to main content
Glama

Google_search_console

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 declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds significant behavioral detail: it reads from daily snapshots, explains the response structure (tracked[], expired[], snapshot_dates[]), notes the 60-day TTL, and clarifies that decay numbers come from daily closes not intraday. No contradictions.

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 key question and is well-structured, but it is verbose with some details (e.g., the signed nature of edge_pp_net, expiration details). Every sentence adds value, but could be slightly trimmed without losing meaning.

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 compensates by thoroughly describing the response fields (tracked with time-series, trend, decay; expired with lifespan; snapshot_dates) and limits (TTL, snapshot start). It is fully adequate for an agent to understand what the tool returns.

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 coverage is 100% with descriptions for both parameters. The description adds value by confirming defaults (days default 14, max 30; window default '1wk'), listing explicit options for window ('24hr | 1wk | 1mo'), and noting clamping behavior. This goes slightly 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 provides 'edge persistence and decay telemetry' and answers a specific question about edge longevity. It distinguishes itself from sibling tools like polymarket_edges by focusing on historical time-series and trend analysis, not just current edges.

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 gives clear context on when to use (to evaluate if an edge is fresh or decaying) but does not explicitly state when not to use it or provide direct alternatives. The contrast between 'fresh wide edge' and '3-week-old wide edge' implies usage, but lacks explicit exclusions.

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

All Google_search_console 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
Disambiguation3/5

Most tools have distinct purposes within their own clusters, and the GSC tools are clearly separated. However, ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, and the several Polymarket tools (arbitrage, edges, fill_risk, kalshi_spread) can be confused without reading each description closely.

Naming Consistency3/5

Names are broadly snake_case and readable, with some useful prefixes (gsc_, polymarket_, pipeworx_). But conventions are mixed: some are verb_noun (list_subscriptions, resolve_entity), some are noun_compound (bet_research, entity_profile), and some are bare verbs (forget, recall), which prevents a predictable pattern.

Tool Count2/5

35 tools is heavy for any single server, but it is especially problematic given the server is named Google_search_console while only 4 of the 35 tools actually relate to Search Console. The rest form a sprawling Pipeworx/Polymarket research toolkit that would be far more coherent as its own server.

Completeness2/5

Relative to the stated Google Search Console purpose, the set is missing common operations such as submitting/removing sitemaps, requesting indexing, or managing URL inspections. The unrelated Pipeworx tools are extensive in their own domains but do not fill these gaps, leaving the GSC surface incomplete.

Resources