Skip to main content
Glama

Censtatd Hk

by io.github.pipeworx-io

Polymarket Fill Risk

polymarket_fill_risk
Read-onlyIdempotent

Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of market (single-market mode) or event (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000 — max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, and a verdict (clean|degraded|cannot_fill). BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio, profit_usd at executed size, per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500 — theoretical overround on thin books is not capturable, and partial basket fills convert an arb into an unhedged directional position (the dominant loss mode in real arb-bot P&L).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideNoSingle-market: buy_yes | sell_yes | buy_no | sell_no (default buy_yes). Basket: sell_yes | buy_yes (default auto — sell if partition sum > 1, buy if < 1).
eventNoBasket mode: event slug or full polymarket.com URL — checks every leg of the partition.
marketNoSingle-market mode: market slug or full polymarket.com URL.
size_usdNoSingle-market: USD to spend (buys) or target proceeds (sells). Basket: settlement notional — shares per leg, each paying $1 at resolution. Default 1000, clamp 10–1,000,000.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate readOnly, openWorld, idempotent, nondestructive. Description adds valuable behavioral context like walking the ladder, returning verdicts (clean/degraded/cannot_fill), forced directional risk, and thin_legs, enhancing transparency.

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

Conciseness5/5

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

Well-structured with clear sections for single-market and basket modes. Dense but every sentence adds value, no fluff. Front-loads key purpose and required parameters.

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?

No output schema, but description comprehensively lists returned fields for both modes (top_of_book, vwap_fill_price, capture_ratio, profit_usd, thin_legs, etc.) and explains forced directional risk. Fully covers what agent needs to know.

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%. Description adds meaning beyond schema by explaining side defaults for basket mode (auto from partition sum), size_usd interpretation (max spend vs target proceeds for singles, settlement notional for basket), and parameters format (slug/URL).

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 it performs a 'realizable-vs-theoretical edge check against live CLOB order-book depth' and distinguishes single-market from basket modes with specific return fields for each.

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

Usage Guidelines5/5

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

Explicitly instructs to use this tool before acting on polymarket_arbitrage signals or trades above ~$500, and explains risks of partial fills and uncapturable overround, providing clear when-to-use guidance.

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

All Censtatd Hk 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
Disambiguation4/5

Most tools target a distinct action or resource, and the long routing descriptions make choices like ask_pipeworx vs ask_pipeworx_grounded vs deep_research clear. The main weak spots are ask_pipeworx_beta being currently identical to ask_pipeworx and the six overlapping Polymarket tools, but each has a discernible workflow.

Naming Consistency3/5

Naming has internally consistent subfamilies such as censtatd_*, ask_pipeworx*, and polymarket_*, but overall it mixes verb-first names (get_table, validate_claim, subscribe), noun-first names (entity_profile, bet_research, pipeworx_feedback), and bare imperatives (remember, forget, recall). The set is readable but does not follow one convention.

Tool Count2/5

35 tools exceeds the 25+ threshold and feels heavy, especially since many tools (generate_llms_txt, scan_dependency, pipeworx_feedback, pipeworx_trending) are unrelated to the HK Census core implied by the server name. The broad Pipeworx scope explains the width, but the surface is still large for an agent to navigate efficiently.

Completeness4/5

For a read-only research/data-access gateway, coverage is strong: generic lookup, grounded verification, deep research, entity profile/compare/change, entity resolution, memory, and subscription lifecycle are all represented. Minor gaps exist, such as no subscription update, no explicit bulk/export path, and fewer HK C&SD convenience wrappers, but agents can work around them.

Resources