Skip to main content
Glama

Vimeo

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

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

The description extensively documents behavior beyond annotations (readOnly, idempotent, not destructive), including data sources (daily snapshots), response structure (tracked, expired, snapshot_dates), limits (60-day TTL, data gaps), and interpretation of decay numbers.

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-structured with a clear purpose at the start, followed by precise details on response and limits. Every sentence adds value, though slight wordiness could be trimmed.

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 two parameters and no output schema, the description fully explains the response format (tracked, expired, snapshot_dates arrays), field meanings, and data limitations, making it sufficient for correct tool usage.

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 description adds default values (14 days, '1wk') and constraints (clamp 2-30) but the input schema already includes these details, so minimal additional value beyond schema coverage.

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 when an edge has existed and if it's shrinking, distinguishing it from sibling tools like polymarket_edges which likely give 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 (e.g., 'a fresh wide edge and a 3-week-old wide edge are different trades') but does not explicitly list alternatives or when not to use.

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

All Vimeo 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.1/5.0
Disambiguation2/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicates, and the polymarket_* family has six tools with blurred boundaries. The Vimeo tools are distinct, but the massive unrelated Pipeworx set creates ambiguity about which tool is appropriate for a given task.

Naming Consistency2/5

Tool names mix conventions: Vimeo tools use bare nouns (video, channel, user), while Pipeworx tools use verb_noun (resolve_entity, validate_claim) or noun_verb (ai_visibility_check). Some names like ask_pipeworx and pipeworx_feedback do not follow a consistent verb-first pattern.

Tool Count2/5

40 tools is far too many for a Vimeo server; only 9 tools are Vimeo-related, and the remaining 31 are an unrelated Pipeworx data toolkit. This inflates the surface area and makes the set unwieldy.

Completeness2/5

The Vimeo surface covers read operations (search, get, list) but lacks any write operations like upload, update, or delete videos. It also misses common Vimeo features like comments, likes, or portfolio management, so common tasks would hit dead ends.

Resources