Skip to main content
Glama
Sign In
AlgoChains MCP Server

AlgoChains MCP Server

Official
by AlgoChains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_polymarket_high_volume

Read-onlyIdempotent

Identify Polymarket markets with the highest 24-hour trading volume to spot active YES/NO opportunities and discover liquid markets.

Instructions

List highest 24h-volume Polymarket markets right now (real Gamma API). Useful for Roo-style early YES/NO flow and liquidity discovery.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv22.7.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is clear. The description adds value by noting 'right now' (real-time data) and 'real Gamma API' (source), but does not provide additional behavioral details like pagination or rate limits beyond what annotations cover.

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?

The description is two sentences long with no filler. The first sentence front-loads the action and target, the second provides usage context. Every word earns its place.

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?

Given the simple schema (one optional parameter) and no output schema, the description provides sufficient context for a basic read tool. It explains what data is returned (highest volume markets) and when to use it. However, it omits details about output structure or how results are ordered, which could be inferred from the description.

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

Parameters2/5

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

The only parameter, 'limit', has a default value of 20 but no description in the schema (0% coverage). The tool description does not mention the parameter at all, leaving the agent to infer its meaning from the name alone. This is a significant gap for parameter understanding.

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 clearly states the verb 'List', the resource 'Polymarket markets', and the specific filter 'highest 24h-volume'. It distinguishes itself from sibling tools like list_polymarket_markets and search_prediction_markets by focusing on volume-based ranking. The mention of 'real Gamma API' adds credibility.

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 provides explicit usage context: 'Roo-style early YES/NO flow and liquidity discovery.' This tells the agent when this tool is beneficial. However, it does not explicitly state when not to use it or name alternative tools, though the purpose implies alternatives for non-volume-based queries.

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