Skip to main content
Glama

Biosamples

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).

TDQS

A4.2/5.0
Behavior4/5

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

Annotations mark readOnlyHint, idempotentHint, and nondestructive. Description adds details: snapshots have 60-day TTL, decay from daily closes (not intraday), and gaps from cache misses. No contradictions with annotations. Extends transparency beyond defaults.

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?

Description is detailed but not verbose; each section (purpose, response format, limits) earns its place. Front-loaded with core question, though could trim some repetition (e.g., snapshot dates explanation). Still well-structured and efficient.

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?

No output schema, but description comprehensively explains response fields (tracked[], expired[], snapshot_dates[]) with attributes like trend, decay rate, lifespan. Also covers data gaps and TTL limits. Complete for a read-only telemetry 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?

Schema covers both parameters with descriptions. Description adds additional context: default values, clamp for days, and why window family matters. Adds modest value beyond schema, consistent with baseline for high 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?

Description clearly states it provides edge persistence and decay telemetry from daily snapshots, answering a specific question about edge longevity. It distinguishes itself from sibling polymarket_edges by focusing on time-series and decay rather than current edge values.

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?

Provides context on when to use (to assess edge age and decay), contrasting fresh vs old edges for trade decisions. Does not explicitly list alternatives or when not to use, but sibling tools imply polymarket_edges for current edges, so guidance is adequate.

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

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

Many tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants (beta currently identical), and the set includes five-plus prediction-market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research) with fuzzy boundaries. Long descriptions help, but an agent selecting among them would frequently struggle to pick the right one.

Naming Consistency3/5

Names are uniformly lowercase snake_case, but the pattern is inconsistent: verb_first names (search_samples, validate_claim, resolve_entity) mix with noun-style names (entity_profile, pipeworx_trending, polymarket_arbitrage) and bare imperatives (remember, recall, forget, subscribe). It is readable, but there is no predictable verb_noun convention across the set.

Tool Count2/5

33 tools is well over the coherent range, and the count is especially inflated because the server is named Biosamples yet only two tools (search_samples, get_sample) actually belong to that domain. The remaining 31 tools are an unrelated mix of Pipeworx research, prediction-market, memory, and subscription utilities, including redundant variants.

Completeness2/5

For the stated Biosamples purpose, only search and retrieve exist—no submission, update, or batch operations—so the domain surface is a read-only fragment. For the broader accidental scope of the other tools, the set is a grab bag with no coherent lifecycle, leaving significant gaps regardless of which domain is considered primary.

Resources