Skip to main content
Glama
Sign In

Polymarket & Kalshi Arbitrage MCP

by io.github.ralf9090
OverviewDiscussionsAdmin

github_intel

Read-onlyIdempotent

GitHub repository & open-source competitive intelligence. Pass 'owner/repo' for deep repository metrics and latest releases, or a keyword topic to find the fastest-growing repositories.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "github_intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of repositories when searching by topic (1-15, default: 5)
queryYesRepository 'owner/repo' (e.g., 'vercel/next.js') OR search topic (e.g., 'mcp server')
x_api_keyNoOptional ak_live_... 30-day Prepaid API Pass key to unlock the full unmasked dataset
payment_signatureNoOptional x402 v2/v1 Base64 or JSON EIP-3009 USDC payment signature to unlock the full unmasked dataset directly via MCP

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the safety profile is handled. However, the description omits a significant behavioral trait visible only in the schema: results are masked unless an x_api_key or payment_signature unlocks the full dataset. With annotations carrying safety, a 3 is appropriate given the undisclosed paid/masked tier.

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?

Two tight sentences, front-loaded with the resource and scoping the two modes in the second. Zero filler, though it is short enough that it could carry one more line of operational context at little cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only open-world intel tool with no output schema, the description is workable but leaves gaps. It hints at returns ('metrics and latest releases') but never addresses the masked-vs-unmasked dataset distinction or rate limits, which an agent calling this paid-tier tool would benefit from knowing.

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?

Schema description coverage is 100%, so the schema already documents query, limit, and the two payment parameters. The description reinforces the dual interpretation of `query`, which is useful, but adds no syntax or format detail beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb/resource: GitHub repository and open-source competitive intelligence, and immediately names the two operating modes (owner/repo metrics vs. topic discovery). It is clear and distinguishable from siblings like domain_intel or package_audit, though the 'competitive intelligence' framing is slightly glossy.

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?

Explicitly tells the agent how to select each mode: pass 'owner/repo' for deep metrics/releases, or a keyword topic to find fastest-growing repos. That is clear usage context, but it offers no when-not guidance or named alternatives among the sibling tools.

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

All Polymarket & Kalshi Arbitrage MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources