Skip to main content
Glama

Uk Parliament

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

A3.9/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds valuable context: snapshots are written on cache-miss (gaps), decay numbers are from daily closes (not intraday), and response structure details.

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?

Well-structured with front-loaded purpose, followed by args, response format, and limits. Every sentence is informative, though slightly dense for quick scanning.

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?

Very comprehensive: explains response fields (tracked, expired, snapshot_dates), limits (60-day TTL), and specific behaviors (decay computation, gap reasons). Handles the complexity of a time-series analysis tool well without an output schema.

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% with clear descriptions. Description adds meaning by explaining defaults, clamps, and how each parameter relates to snapshot families (e.g., 'window' is a snapshot family). Minor inconsistency between 'max 30' and schema's 'clamp 2-30' but not contradictory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it provides 'edge persistence and decay telemetry' and answers specific questions about edge age and shrinkage. However, it does not explicitly differentiate itself from the sibling 'polymarket_edges' tool, though it is implied as a derived analysis.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes the context (e.g., 'a fresh wide edge and a 3-week-old wide edge are different trades') and provides limits (60-day TTL). Lacks explicit when-not-to-use or alternative tool suggestions.

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

All Uk Parliament 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.4/5.0
Disambiguation2/5

Several tools are near-duplicates (ask_pipeworx and ask_pipeworx_beta are currently identical; ai_visibility_check vs scan_competitor_ai_presence overlap), and the massive mix of unrelated domains (Polymarket betting, general data lookup, AI visibility) alongside UK Parliament tools makes selection confusing. An agent would struggle to know whether to use ask_pipeworx, ask_pipeworx_beta, or ask_pipeworx_grounded, or which of the five polymarket tools fits.

Naming Consistency3/5

Most tools use snake_case with readable names, but the action placement varies (verb_noun like get_bill vs noun_verb like bet_research, entity_profile), and there are compound names like generate_llms_txt and scan_competitor_ai_presence. The style is mostly consistent but the verb_noun pattern is not uniform across the set.

Tool Count2/5

38 tools is heavy, and the overwhelming majority are unrelated to the server's stated UK Parliament purpose. Only 7 tools (get_bill, search_bills, bill_stages, get_member, search_members, search_hansard, recent_divisions) have anything to do with Parliament, making the count wildly inappropriate for the apparent scope.

Completeness2/5

The Parliament-specific surface is thin: basic bill/member/Hansard lookups exist, but there are no tools for specific divisions/votes, committees, publications, or detailed procedural information. The vast non-Parliament tooling is irrelevant, creating a dead end for any real Parliament research beyond the basics.

Resources