Skip to main content
Glama

Confluence

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

TDQS

A4.7/5.0
Behavior5/5

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

Annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint false) are consistent with description. Description adds extensive behavioral details: snapshot TTL (60 days), decay computation from daily closes not intraday, response structure for tracked vs expired opportunities.

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?

Well-structured with clear sections (RESPONSE, LIMITS). Front-loaded with core purpose. Every sentence contributes meaningful information without redundancy.

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?

Despite no output schema, description thoroughly explains response fields (tracked, expired, snapshot_dates) with details on trend, decay, lifespan. Covers limits and assumptions completely for a tracking tool.

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, but description adds context: default/max days, window family meanings, and explanation of gaps due to cache-miss. Adds value beyond 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?

Description explicitly states it provides edge persistence and decay telemetry, answering a specific question about edge duration. It distinguishes itself from sibling tool 'polymarket_edges' by focusing on time-series tracking.

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?

Explanation of when to use is clear (understand edge persistence vs decay). Implicitly suggests when not to use (for single snapshot edges, use polymarket_edges), but lacks explicit alternatives or exclusion criteria.

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

All Confluence 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

B3.4/5.0
Disambiguation2/5

The set is dominated by near-overlapping research tools: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all answer factual questions with heavily overlapping descriptions, and the six polymarket_* tools plus bet_research form a second confused cluster. The five confluence_* tools are distinct, but an agent would struggle to pick among the research/betting alternatives without reading thousands of words of caveats.

Naming Consistency2/5

Most names are snake_case, but the conventions are mixed: verb_noun (confluence_create_page, validate_claim), noun_verb (bet_research), prefixed nouns (polymarket_arbitrage, pipeworx_feedback), and bare verbs (recall, forget). The glaring issue is that the server is named Confluence yet only 5 of 36 tools carry the confluence_ prefix, leaving the other 31 tools with no thematic prefix and no consistent pattern.

Tool Count2/5

36 tools is already in the 'too many' range, but the mismatch is deeper: only 5 tools relate to Confluence while 31 tools cover an entirely different domain (Pipeworx data research, prediction markets, subscriptions). For a wiki server this is wildly over-scoped; as a combined surface it is bloated and lacks a unifying purpose.

Completeness2/5

For the Confluence domain the surface is incomplete: pages can be created, fetched, listed, and searched, but there is no update_page, delete_page, comment, attachment, or content-type coverage, leaving obvious CRUD dead ends. For the Pipeworx domain, coverage is broad but disorganized, with overlapping research paths and no clear hierarchy.

Resources