Skip to main content
Glama

DexPaprika

by com.dexpaprika.mcp

getTokenMultiPrices

Read-onlyIdempotent

Get current USD prices for up to 10 tokens on the same network in one batched call, returned as a prices array plus a missing_tokens list. Read-only and keyless. Tokens that cannot be priced come back in missing_tokens rather than being dropped, so check that list for partial failures. Use for 'prices for these tokens', 'compare the price of X, Y and Z', or building a portfolio/dashboard snapshot. For one token with full metadata and multi-timeframe stats use getTokenDetails. Params: network (required slug, all tokens must share it); tokens (required array of 1 to 10 contract addresses).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokensYesREQUIRED: Up to 10 token contract addresses on the same network.
networkYesREQUIRED: Network ID from getNetworks
rationaleYesREQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions` field for the full convention and worked examples.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive traits. The description adds 'Read-only and keyless' (no API key needed) and explains that unpriceable tokens appear in 'missing_tokens' list, signaling partial failures. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences: purpose, output behavior, usage guidance. Front-loaded with the key action and constraints. No fluff, each sentence adds unique value. Could be slightly more structured with explicit sections, but 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?

No output schema exists, but the description details the return structure (prices array, missing_tokens list). Covers partial failures and usage guidance. Parameter list is complete. For a simple fetch tool with good sibling context, this is 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 description coverage is 100%—all parameters have descriptions. The description adds meaning by restating constraints: network is a 'required slug, all tokens must share it', tokens are 'required array of 1 to 10 contract addresses'. This reinforces schema info and clarifies cross-parameter dependency.

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 'Get', resource 'current USD prices', scope 'up to 10 tokens on the same network', and key output details ('prices array plus a missing_tokens list'). It distinguishes from sibling getTokenDetails by specifying the single-token, multi-timeframe alternative.

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

Usage Guidelines5/5

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

Explicitly lists use cases: 'prices for these tokens', 'compare the price of X, Y and Z', 'portfolio/dashboard snapshot'. Provides a clear alternative: 'For one token with full metadata and multi-timeframe stats use getTokenDetails'.

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

All DexPaprika toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose: network listings, DEX listings, pool discovery, pool snapshots, OHLCV, transactions, token details, multi-price, token pools, search, stats, and feedback. Potential overlaps like getTopTokens vs filterNetworkTokens are explicitly disambiguated in descriptions.

Naming Consistency4/5

Mostly follows camelCase verb-first pattern (getNetworks, getPoolDetails, getTokenMultiPrices). However, the pair filterNetworkTokens and getNetworkPoolsFilter are inconsistently structured; the latter should logically be filterNetworkPools for full consistency.

Tool Count4/5

At 17 tools, it slightly exceeds the ideal 3-15 range, but each tool covers a distinct data operation for a comprehensive DEX-market API. The count feels justified given the breadth of features, though it is on the heavier side.

Completeness4/5

The domain of read-only DEX analytics is well covered: networks, DEXes, pools, tokens, search, stats, and per-pool history. Minor gaps exist, such as no direct token price history endpoint, but pool OHLCV and token details cover most needs.

Resources