Skip to main content
Glama

Jpl Ssd

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

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

Annotations already indicate read-only, open-world, idempotent, non-destructive. Description adds limitations (60-day TTL, start date), data sources (daily closes, not intraday), and handling of gaps, enhancing transparency beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is detailed but dense, with extensive response field descriptions that could be shortened. Structure is logical with sections, but length detracts from quick consumption.

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 no output schema, description thoroughly explains response fields (tracked, expired, snapshot_dates) and limitations, making it complete for an agent to understand tool behavior.

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 fully (100% coverage). Description reaffirms defaults and ranges but adds little new meaning beyond what schema provides.

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?

Clearly states it tracks edge persistence and decay telemetry, contrasting fresh vs old edges, and distinguishes from sibling polymarket tools by focusing on edge history rather than current edges or arbitrage.

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 (when edge age matters) and interpretive guidance, but does not explicitly mention alternatives like polymarket_edges or when not to use this tool.

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

All Jpl Ssd 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.5/5.0
Disambiguation2/5

Multiple tools overlap in purpose, especially the ask_pipeworx variants and the polymarket_* tools. An agent would struggle to distinguish between similar functions, increasing the risk of selecting the wrong tool.

Naming Consistency2/5

Tool names use inconsistent conventions: some are snake_case (close_approaches), some are verb_noun (generate_llms_txt), and others mix styles (ask_pipeworx vs. deep_research). No clear pattern is maintained across the set.

Tool Count1/5

At 35 tools, the server is bloated and unfocused. The majority of tools are unrelated to the 'Jpl Ssd' domain, which only has 4 relevant tools. The count is far too high for the stated purpose.

Completeness2/5

The JPL SSD coverage is minimal (only 4 tools), missing key functionalities like detailed object queries or bulk downloads. The remaining tools cover unrelated domains, so the surface is both incomplete for its primary domain and cluttered with off-topic tools.

Resources