Skip to main content
Glama

Pair data

pair_data
Read-only

Get full DEXScreener stats for a token: price, 5m/1h/6h/24h volume, buy/sell counts, liquidity, market cap, and price changes. Returns the highest-volume pair. Costs $0.001 USDC per call.

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": {
      "tokenAddress": "<tokenAddress>"
    },
    "name": "pair_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYesToken mint/contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already disclose readOnlyHint=true and openWorldHint=true, so the description does not need to repeat safety basics. It adds meaningful behavioral context by stating that it returns the highest-volume pair and costs $0.001 USDC per call, though it does not cover rate limits or failure-charge behavior.

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 efficient sentences, front-loaded with the core function and followed by return fields, pair-selection behavior, and cost. Every sentence adds useful information.

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

Completeness5/5

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

For a simple one-parameter read-only tool with no output schema, the description is complete enough: it enumerates the returned stats, explains which pair is selected, and discloses the per-call cost. An agent has enough information to decide to call it and invoke it correctly.

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%, and the single tokenAddress parameter is already documented in the schema. The description says 'for a token' but adds no format or validation detail beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource: 'Get full DEXScreener stats for a token.' It also names the exact stats returned and clarifies that the tool returns the highest-volume pair, which distinguishes it from generic price or liquidity 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 usage context is implied: use this to fetch full DEXScreener stats for a token. However, it does not explicitly say when to use this instead of nearby siblings such as token_price, dex_liquidity, or token_metadata, nor does it state exclusions.

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