Skip to main content
Glama

Tatoeba

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?

Beyond the readOnly/idempotent annotations, the description explains snapshot gaps, TTL limits, decay calculation from daily closes, signed edge values, and the meaning of expired opportunities. This gives substantial behavioral transparency that annotations alone would not 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 and dense, but every sentence carries meaningful information. It is structured with labeled sections (Args, RESPONSE, LIMITS) and front-loaded with the core purpose. Slight verbosity prevents a 5, but there is no filler.

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?

There is no output schema, yet the description fully specifies the response shape (tracked[], expired[], snapshot_dates[]), their fields, and important limitations such as TTL and gap behavior. This is complete for a telemetry-focused 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 documents both parameters with descriptions and defaults (100% coverage). The description repeats the defaults and adds the 'max 30' clamp for 'days', but does not significantly extend the semantic meaning beyond the schema, 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 this is edge persistence and decay telemetry built from daily polymarket_edges snapshots, with a specific question it answers ('how long has this edge existed and is it shrinking?'). It distinguishes itself from the sibling polymarket_edges tool by focusing on time-series behavior rather than a current edge snapshot.

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 implies when to use the tool: when you need to understand edge persistence/decay over time, contrasting fresh vs. old wide edges. It does not explicitly name alternatives or exclusion criteria, but the emphasis on snapshot history and decay makes the use case clear.

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

All Tatoeba 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/5.0
Disambiguation2/5

Many tools have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_grounded, deep_research; multiple Polymarket tools). The memory tools (remember/recall/forget) are generic and could be confused with each other. Overall, there is significant ambiguity in tool selection.

Naming Consistency3/5

Most tool names use snake_case, but there is no strong verb_noun pattern. Some are simple nouns (languages, search) while others are verbs (forget, recall). The naming is readable but not highly consistent.

Tool Count1/5

With 34 tools, the set is far too large for a Tatoeba server. Only 4 tools (search, sentence, translations, languages) are actually related to Tatoeba; the rest cover unrelated domains (Pipeworx data, Polymarket, AI visibility). This is an extreme mismatch.

Completeness2/5

For the Tatoeba domain, the 4 tools cover basic functionality but lack operations like adding or editing sentences. The overwhelming presence of irrelevant tools makes the surface feel incomplete and disjointed for the server's stated purpose.

Resources