Skip to main content
Glama
Sign In

Polymarket & Kalshi Arbitrage MCP

by io.github.ralf9090
OverviewDiscussionsAdmin

defi_yields

Read-onlyIdempotent

DeFi highest APY & yield radar powered by DeFiLlama. Finds top lending and liquidity pools for any token (USDC, ETH, USDT, WBTC) filtered by blockchain and minimum TVL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "defi_yields"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain name such as 'Base', 'Ethereum', 'Arbitrum', 'Solana', or 'all' (default: 'Base')
limitNoNumber of top pools to return (1-20, default: 5)
symbolNoToken symbol to earn yield on (default: 'USDC')
x_api_keyNoOptional ak_live_... 30-day Prepaid API Pass key to unlock the full unmasked dataset
min_tvl_usdNoMinimum pool TVL in USD for safety filtering (default: 100000)
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only the DeFiLlama provenance; it omits notable behavior such as the masked free dataset versus the paid/unmasked unlock path, which lives only in the parameter descriptions.

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 compact sentences, front-loaded with the capability and followed by the filtering scope. Minimal waste; phrasing is slightly marketing-flavored ('radar', 'powered by') but still informative.

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

Completeness4/5

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

For a read-only query tool with all six parameters fully documented in the schema and a complete safety annotation set, the definition is sufficient. The free-vs-paid data masking nuance is covered by the schema parameter descriptions, so the omission from the prose is minor.

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 baseline is 3. The description's token examples (USDC, ETH, USDT, WBTC) and the chain/TVL filter mention largely restate what the schema already documents, adding no syntax or default guidance beyond it.

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 ('Finds') and resource ('top lending and liquidity pools') plus the data source (DeFiLlama), which cleanly separates it from siblings like defi_swap_quote or token_alpha. It does not explicitly name a sibling to avoid, but the resource is unambiguous.

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

Usage Guidelines3/5

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

The description implies when it is relevant ('for any token... filtered by blockchain and minimum TVL') but never states when to prefer it over alternatives or any prerequisites. Usage is inferable rather than spelled out.

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