Skip to main content
Glama

Guild Wars 2

by io.github.pipeworx-io

Polymarket Arbitrage

polymarket_arbitrage
Read-onlyIdempotent

Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a trending_scan of the top ~200 markets by weekly volume; pass event for the strongest per-event partition_check, or topic for a themed cross-event scan. event (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k"; walks child markets, checks date-axis / threshold-axis ordering AND computes the partition_check (sum of YES prices across mutually-exclusive legs — should ≈1; deviations >3pp emit a BUY/SELL EVERY LEG signal). topic (for cross-event scanning): pass a seed question like "Strait of Hormuz traffic returns to normal" or "Fed rate decision"; searches related events across the platform, flattens markets, runs the comparator on the union. Cross-event mode catches "...by May 31" vs "...by Jun 30" patterns that single-event misses. SEMANTIC ANCHOR: cross-event pairs require ≥0.30 Jaccard similarity on question tokens (prevents Powell-Fed-Pause being paired with Powell-DOJ-probe); skipped_low_similarity surfaces the rejected pair count. PARTITION FILTER: drops will-person-X / will-manager-Y / will-someone-else- placeholder slugs; partitions with >20% placeholder fraction return null arb signal. Response: opportunities[] (gap_pp, suggested_trade, reasoning, monotonicity violation context), and in event mode partition_check{sum_yes_prices, gap_from_1, placeholders_filtered, suggested_trade}. FILL CHECK: when the partition signal fires, arbitrage.fill_check prices it against live CLOB depth (theoretical_edge_pp_at_book vs realizable_edge_pp at 1000 shares/leg, thin_legs[]) — realizable_edge_pp ≤ 0 means the overround exists only at last-trade, not in the book; do not trade it. For custom sizing use polymarket_fill_risk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventNoSingle-event mode (use this if you know the specific Polymarket event): event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k". Full Polymarket URLs also accepted.
topicNoCross-event mode (use this if you want to scan related events across the platform): a topic or seed question like "Fed rate decision" or "Strait of Hormuz traffic returns to normal". Tool searches Polymarket for related events and checks monotonicity across them.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds rich behavioral context: semantic anchor Jaccard threshold, partition filter for placeholder slugs, fill check against live CLOB depth, and conditions for null signals. 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.

Conciseness4/5

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

The description is thorough but slightly verbose; however, every sentence adds value. It is front-loaded with the main purpose and structured logically by mode. A more compact version could convey the same information, but it is not excessively long.

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 clearly outlines the response structure: opportunities array with fields, partition_check object in event mode, and fill_check details. It covers edge cases like placeholder filters and similarity thresholds. The tool is complex, and the description provides sufficient completeness for an agent to understand inputs, behavior, and outputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters have descriptions. The description adds significant context: event takes a slug or full URL, topic takes a seed question, and each parameter triggers a different scanning mode. It explains how the parameters affect the analysis, going well beyond 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 explicitly states the tool's purpose: 'Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks.' It clearly distinguishes three modes of invocation (no args, event, topic) and differentiates from sibling tools like polymarket_fill_risk.

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?

The description provides explicit guidance on when to use each mode: 'Call with NO args for a `trending_scan`', 'pass `event` for the strongest per-event partition_check', 'pass `topic` for a themed cross-event scan.' It also warns against acting on signals with low realizable edge and refers to polymarket_fill_risk for custom sizing.

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

All Guild Wars 2 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

C2.8/5.0
Disambiguation2/5

The set mixes two unrelated domains (Guild Wars 2 endpoints and a broad Pipeworx data-research suite), and within each there are near-duplicates: ask_pipeworx vs ask_pipeworx_beta are functionally identical, commerce_prices vs guild_wars_2_item_price vs commerce_listings overlap on Trading Post data, and ask_pipeworx/ask_pipeworx_grounded/deep_research all route questions to the same source catalog. An agent could easily select the wrong tool.

Naming Consistency3/5

Names are all snake_case and readable, but there is no consistent pattern: some are bare nouns (achievements, currencies, quaggans, worlds, build), some are verb_noun (resolve_entity, validate_claim, generate_llms_txt), some are ask_* (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded), and some are compound names (polymarket_kalshi_spread, guild_wars_2_item_price). Minor deviations would be fine, but this is a genuine mix of conventions.

Tool Count2/5

42 tools is far beyond the well-scoped range, and the majority are unrelated to the 'Guild Wars 2' server name (only ~11 tools are GW2 API endpoints; the rest are Pipeworx data-research/meta tools). This feels like two or three servers merged into one.

Completeness2/5

For a Guild Wars 2 server, the coverage is thin: it has items, prices, achievements, worlds, and WvW, but no recipes, guilds, characters, skills, maps, or PvE content. For the broader data-research domain implied by most tools, the surface is sprawling but still lacks depth in several areas. The result is a set that is neither complete for GW2 nor coherently scoped for anything else.

Resources