Skip to main content
Glama

Faa Regulations

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
Behavior5/5

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

The description goes far beyond annotations (readOnlyHint, idempotentHint) by detailing output structure (tracked, expired, snapshot_dates), sign conventions (edge_pp_net signed), and limitations (60-day TTL, gaps from cache misses). No contradictions with 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?

The description is verbose and packs many details into a long paragraph. It front-loads the purpose but the output structure section could be more concise. Some redundancy exists (e.g., 'days' explanation repeated).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite lacking an output schema, the description fully details the response format (tracked, expired, snapshot_dates) and explains edge behavior. It covers complexity, limits, and data sources, making it fairly complete for a 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 coverage is 100%, so the description adds minimal value beyond defaults and clamping. It mentions default values and constraints (max 30, clamp 2-30) but does not explain nuances beyond 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 the tool's purpose: 'Edge persistence and decay telemetry built from daily polymarket_edges snapshots.' It answers a specific question ('how long has this edge existed and is it shrinking?') and distinguishes itself from sibling tools like polymarket_edges by focusing on time-series tracking rather than current state.

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 provides clear context for when to use this tool, explaining that a fresh wide edge differs from an old one. It does not explicitly list alternatives or conditions to avoid, but the context sufficiently helps an agent decide.

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

All Faa Regulations 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

Multiple tools have unclear boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route to the same 5,714-tool catalog with heavily overlapping purposes, and ask_pipeworx_beta is currently identical to ask_pipeworx. Similarly, bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, and polymarket_fill_risk all target prediction-market analysis and could easily be confused by an agent. The two FAA tools (faa_regulation, faa_search) are distinct, but they are buried among a dozen unrelated data-lookup and memory tools.

Naming Consistency4/5

Most tools follow a consistent lowercase snake_case verb_noun or noun_verb pattern (faa_search, resolve_entity, compare_entities, validate_claim, discover_tools, unsubscribe). Minor deviations exist, such as ask_pipeworx and pipeworx_feedback lacking underscores, and the polymarket_* family mixes noun-led names, but overall the naming is readable and predictable.

Tool Count1/5

33 tools for a server named 'Faa Regulations' is a severe mismatch: only 2 of the 33 tools (faa_regulation, faa_search) relate to FAA regulations, with the rest covering general data lookups, prediction markets, SEC filings, memory storage, npm dependency checking, and llms.txt generation. The count is far too high for the stated domain, and most tools do not belong in this server at all.

Completeness2/5

The actual FAA surface is thin: faa_search provides keyword lookup and faa_regulation returns full text or a part's section list, so basic citation-lookup workflows work, but there is no update/amendment tracking, no browse-by-part navigation beyond a section list, and no related aviation data such as NOTAMs or TFRs. The dominant Pipeworx tool family is unrelated to FAA regulations, so an agent using this server for its apparent purpose would hit dead ends quickly.

Resources