Skip to main content
Glama

Nist Standards

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

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

Annotations declare readOnlyHint, idempotentHint, etc., and the description adds context on data sources, trend computation, and limits (60-day TTL, daily closes). No contradictions.

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 informative and front-loaded with the key use case. It is relatively long but every sentence adds value. Could benefit from slightly more structured formatting.

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, the description comprehensively covers the response fields (tracked, expired, snapshot_dates) and limitations, making it self-contained.

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%, and the description adds meaningful defaults, ranges, and the concept of 'window family', plus explains the response structure which is absent from the 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?

The description clearly states what the tool does: it provides edge persistence and decay telemetry, answering when an edge is shrinking. It distinguishes itself from siblings like polymarket_edges by focusing on time-series analysis.

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?

It specifies default and maximum values for days, the snapshot window family, and gives hints about when to use it (e.g., differentiating fresh vs old edges). However, it does not explicitly exclude alternative tools like polymarket_edges.

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

All Nist Standards 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

A4/5.0
Disambiguation3/5

Most tools have distinct purposes, but several clusters overlap: ask_pipeworx_beta is currently identical to ask_pipeworx, polymarket_arbitrage and polymarket_edges both surface arbitrage opportunities, and validate_claim overlaps with ask_pipeworx_grounded. Descriptions mitigate some confusion, but selection errors are still likely.

Naming Consistency4/5

Names are overwhelmingly lowercase snake_case and descriptive, such as nist_control_family, polymarket_fill_risk, and list_subscriptions. Minor deviations exist with single-word memory verbs like remember/recall/forget and the ask_pipeworx_* variants, but the overall pattern is predictable and readable.

Tool Count2/5

34 tools is well above the comfortable range and includes many tools unrelated to the server's NIST Standards name, such as Polymarket betting, npm dependency scanning, AI visibility checks, and llms.txt generation. The set feels like a broad general-purpose data platform rather than a scoped NIST reference server.

Completeness3/5

For the NIST domain, the three control tools provide id lookup, family listing, and keyword search, but there is no catalog overview or family enumeration, and no comparison, revision, or export capability. The other 31 tools do not fill those gaps, so the NIST surface is functional but not fully complete for compliance workflows.

Resources