Skip to main content
Glama
Sign In
openpulsechain

openpulsechain

Official
by openpulsechain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Top DEX Pairs

get-top-pairs
Read-onlyIdempotent

Retrieve the top PulseX DEX trading pairs sorted by trading volume. Specify a limit up to 500 pairs to get the most active markets on PulseChain.

Instructions

List top PulseX DEX trading pairs by 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": "get-top-pairs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of pairs (default 20, max 500)

Output Schema

NameRequiredDescriptionDefault
pairsYesArray of top trading pairs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds no further behavioral details (e.g., data freshness, pagination, or rate limits) beyond what annotations provide.

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 sentence with no wasted words. It front-loads the key action and resource, making it easy to scan.

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 presence of an output schema and the simplicity of the tool (one optional parameter, annotations cover behavior), the description is sufficient. It could optionally mention that results are sorted by volume, but that is implied by 'top pairs' and the tool's name.

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 coverage is 100% for the single parameter 'limit', which is clearly described with default and max values. The description does not mention parameters, but the schema already documents them adequately. Baseline 3 is appropriate.

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 uses a specific verb 'List', identifies the resource as 'top PulseX DEX trading pairs', and specifies the criterion 'by volume'. This clearly distinguishes it from siblings like 'get-top-tokens' and 'get-pair-analytics'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. For example, it does not suggest that this is for volume-based ranking or when to prefer other tools like 'get-pair-analytics'.

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