Skip to main content
Glama

Youtube

by io.github.pipeworx-io

Polymarket–Kalshi Spread

polymarket_kalshi_spread
Read-onlyIdempotent

Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says so. TWO MODES: (1) topic — 10 pre-mapped macro shortcuts ("fed", "btc", "cpi", "gdp", "sp500", "recession", "next_pope", "next_uk_pm", "next_israel_pm", "2028_president") auto-fetch the matching event on each venue. (2) explicit kalshi_event_ticker + polymarket_event_slug for custom pairings — BOTH modes run the identical token-overlap matcher, so the same disclosures apply to both. RESPONSE: each venue's leg-by-leg prices (raw probability 0-1) plus matched spread[].top_spreads_pp (Kalshi − Polymarket) where the same outcome shows up on both sides. SAFETY FIELDS: compatibility_warning is a sentence and compatibility_codes[] the machine-readable form; BOTH can be non-empty on returned pairs, so read them even when matched_pairs>0. Codes: event_subject_mismatch (the two event titles share no subject words — probably not the same question), temporal_mismatch (they resolve in different months), temporal_alignment_unknown (the resolution month could not be parsed on one or both sides — NOT the same as confirmed-aligned; check each event's close/strike date yourself), non_equivalent_bet_shapes, no_candidate_pairs, unclassified_legs_excluded, pairing_unverified (set in EITHER mode whenever pairs are returned: the legs were matched by keyword and word overlap, not a shared resolution source). Each entry in top_spreads_pp carries its own flags[] (temporal_mismatch, temporal_alignment_unknown, event_subject_mismatch, low_token_overlap). A leg whose metric_type or match_subtype is "unknown" is NEVER paired — those comparisons land in spread.skipped_unclassified and, when the wording lined up, in spread.low_confidence_pairs[] for inspection only. temporal_alignment{polymarket_month,kalshi_month,aligned} tells you whether the two events resolve in the same calendar period, in EITHER mode; null means it could not be computed (see temporal_alignment_unknown), not that the two sides align. spread.fees_note is a standing disclosure: Kalshi charges per-contract trading fees, Polymarket does not, and this tool does not model Kalshi's fee schedule — every spread_pp is gross, not a net tradeable edge. skipped_cross_type / skipped_cross_subtype counters expose how many leg-pair comparisons were dropped (cross-type = metric_type mismatch like MoM vs YoY; cross-subtype = inequality mismatch like cum_ge vs cum_le). Real cross-venue spreads are rarer than the macro-shortcut list suggests — most pre-mapped topics return compatibility_warning today; pre-mapped ≠ tradeable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoPre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president
kalshi_event_tickerNoExplicit Kalshi event ticker, e.g. "KXFED-26OCT". Overrides the topic-mapped Kalshi side.
polymarket_event_slugNoExplicit Polymarket event slug, e.g. "fed-decision-in-june-825". Overrides the topic-mapped Polymarket side.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  }
+]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark the tool read-only and idempotent, and the description adds substantial behavioral context: it does not model Kalshi fees, spread values are gross not net, pairs are matched by keyword/word overlap and not a shared resolution source, and unknown metric types are never paired. This goes well beyond what the annotations convey and does not contradict them.

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 long but well-structured with clear section markers like TWO MODES, RESPONSE, and SAFETY FIELDS, and it front-loads the core purpose. Some phrases are slightly redundant, but the density is justified because the tool has no output schema and the interpretation of safety codes is critical.

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 having no output schema, the description fully covers the response shape, safety fields, compatibility codes, per-entry flags, skipped-leg behavior, temporal alignment semantics, and fee caveats. An agent has enough context to invoke the tool and interpret its result correctly without additional documentation.

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?

The input schema already documents all three parameters with 100% coverage, including the topic enum, Kalshi ticker, and Polymarket slug, along with override behavior. The description reinforces that both modes run the same matcher but adds little semantic detail beyond the schema, so the baseline of 3 is appropriate.

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 opening line states the function precisely: 'Cross-venue spread between Kalshi and Polymarket for the same resolving question.' It clearly names the resource, the operation, and the cross-venue scope, which distinguishes it from venue-specific siblings like polymarket_edges and polymarket_arbitrage.

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 explains two invocation modes, when to use the pre-mapped topic shortcuts versus explicit tickers, and warns that most pre-mapped topics currently return compatibility warnings. It does not explicitly name alternative sibling tools or state when to prefer them, but the usage context is clear and actionable.

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

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

The five yt_* tools are distinct, but the majority of the set is dominated by overlapping Pipeworx tools: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical entry points, and the multiple polymarket_* tools cover closely related edge/arbitrage/fill-risk territory. An agent could easily select the wrong one.

Naming Consistency3/5

Most names use lowercase snake_case, but conventions are mixed: yt_* and polymarket_* are prefix-scoped, pipeworx_* mixes verb-first and noun-first names, and there are standalone verbs like remember, recall, and forget. The server is named Youtube, yet the bulk of tools follow unrelated Pipeworx/Polymarket naming.

Tool Count2/5

36 tools is heavy for a server named Youtube, and only 5 actually address YouTube functionality. The remaining 31 tools cover unrelated data-research and prediction-market features, making the surface bloated and off-purpose.

Completeness3/5

The YouTube subset covers search, channel info, channel videos, video details, and comments, which handles basic read-only queries. Missing playlists, captions/transcripts, and subscription/upload actions leave notable gaps for a YouTube-focused server.

Resources