Skip to main content
Glama

rank_polymarket_markets

Rank Polymarket markets by volume, liquidity, or 24h volume.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
sortByNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full transparency burden. It implies a read-oriented ranking operation, but does not state default sort behavior, sort direction, default or maximum limit, pagination, authentication needs, or return format.

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 a single front-loaded sentence with no filler or repetition. It is appropriately concise and immediately communicates the core action.

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

Completeness2/5

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

This is a simple two-parameter tool, but it has no annotations and no output schema. The description does not explain limit semantics, default behavior, return shape, or how it relates to nearby list/search tools, leaving meaningful gaps for an agent trying to invoke it correctly.

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?

Schema description coverage is 0%, so the description must compensate for both parameters. It informally lists allowed sortBy values (volume, liquidity, 24h volume), but it says nothing about the limit parameter, defaults, bounds, or whether limit is required or capped.

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?

The description states a specific verb and resource: rank Polymarket markets by volume, liquidity, or 24h volume. It clearly conveys the operation, but it does not distinguish this tool from siblings such as list_polymarket_markets, search_polymarket_markets, or screen tools.

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 ranking purpose and sort criteria imply when to use it, but there is no explicit guidance on when to choose this over listing or searching Polymarket markets. No exclusions, prerequisites, or alternative-selection rules are provided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources