Skip to main content
Glama

Realestateapi

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. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false. Description adds significant behavioral details: reads snapshots, returns time-series, trend, decay, and explains data sources and limitations. No contradiction 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.

Conciseness4/5

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

Description is detailed but efficiently structured, starting with high-level purpose then diving into response format and limits. Every sentence adds value; however, the response format section is somewhat long but necessary given no output schema.

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, description fully explains the response structure (tracked, expired, snapshot_dates) covering fields, meaning, and edge cases. Also notes limits like 60-day TTL and snapshot gaps. Complete for the tool's complexity.

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 covers 100% of parameters with basic descriptions. Description adds meaning to 'days' (default 14, max 30) and 'window' (snapshot family with examples 24hr, 1wk, 1mo). Enhances understanding 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?

Description clearly states purpose: edge persistence and decay telemetry from daily snapshots. Distinguishes from sibling polymarket_edges by focusing on historical time-series and trends, answering 'how long has this edge existed and is it shrinking?'

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?

Description explains when to use: to assess edge age and decay, contrasting fresh vs old edges. Implicitly indicates not to use for just current edge values (use polymarket_edges instead). Does not explicitly list exclusion criteria but provides clear context.

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

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

Several tools have overlapping purposes: ask_pipeworx and ask_pipeworx_beta are currently identical, deep_research and ask_pipeworx both answer broad factual questions, and the polymarket tools (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, bet_research) cover heavily overlapping edge/arb research territory. An agent could easily route a query to the wrong one.

Naming Consistency2/5

Most tools use snake_case, but there is no consistent verb_noun pattern: ask_pipeworx, deep_research, bet_research, recent_changes, remember/recall/forget, generate_llms_txt, realestateapi_property_detail, and polymarket_edges all follow different structural conventions. The server name Realestateapi also does not match the broader Pipeworx/polymarket tool set.

Tool Count2/5

34 tools is above the 25+ threshold for a heavy, hard-to-navigate surface, especially for a server named Realestateapi where only 3 tools actually concern real estate. Many tools are generic utilities, memory helpers, feedback channels, and prediction-market tooling that feel unrelated to the apparent real-estate API scope.

Completeness2/5

For a real-estate-focused server, the surface is significantly incomplete: property search, property detail, and skip-trace cover only basic owner/value lookups. Missing obvious real-estate capabilities like comparable sales, tax history, market trends, school/flood data, and listing lifecycle operations create notable gaps an agent would need to work around.

Resources