Skip to main content
Glama
Sign In
AlgoChains MCP Server

AlgoChains MCP Server

Official
by AlgoChains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

search_prediction_markets

Read-onlyIdempotent

Search Polymarket and Kalshi markets by keyword to get live contract prices, volume, liquidity, and URLs. Discover current YES/NO odds to make informed predictions.

Instructions

Search live Polymarket and/or Kalshi markets by keyword. Returns real contract YES/NO prices, volume, liquidity, and URLs. Fails closed if no API data.

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": "search_prediction_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesSearch phrase, e.g. Bitcoin Fed election
platformNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv22.7.1

TDQS

A3.9/5.0
Behavior4/5

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

Description adds 'Fails closed' behavior and return fields (prices, volume, liquidity, URLs). Annotations already indicate read-only, non-destructive, and idempotent. The additional failure mode is valuable context beyond annotations.

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?

Two sentences with no waste. First sentence states action and output, second adds failure behavior. Front-loaded and efficient.

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 simple search tool with no output schema, description covers purpose, output fields, and failure mode. Missing parameter details for limit and platform, but those are in schema with defaults. Minor gap but overall sufficient.

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 has 33% description coverage (only query described). Tool description specifies output fields, adding meaning to the purpose. It does not detail limit or platform, but the overall search intent is clear. Adds value by describing return structure.

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?

Clearly states 'Search live Polymarket and/or Kalshi markets by keyword' and specifies returns. Does not explicitly differentiate from sibling get_prediction_markets or list_polymarket_markets, but the verb 'search' conveys a distinct purpose.

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?

Gives a failure note ('Fails closed if no API data') but no guidance on when to use this tool versus alternatives like get_prediction_markets or list_polymarket_markets. Context of use is implied by the description of the tool's function.

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

Deploy Server

Other Tools