DexPaprika: tool descriptions scored com.dexpaprika/dexpaprika

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://mcp.dexpaprika.com/streamable-http
Repository: github.com/coinpaprika/dexpaprika-mcp
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how DexPaprika (com.dexpaprika/dexpaprika)'s tool descriptions scored, the issues found and the names of its tools and parameters. The descriptions are the server's own: read them where the copy came from.

Forecall asked the URL this server lists in the official MCP Registry for its tools/list once, on the date above, without calling any tool. The server may have changed since.

servers/com.dexpaprika/dexpaprika

Average score: 85.3 / 100Clear
Tools: 20
Near-identical descriptions: 2

Across the server

Minor
The server's instructions are 4941 characters. Claude Code reads only the first 2,048 by default (Codex 0.154.0 reads them whole). Put what the server is for first.instructions_long

Tools whose descriptions are nearly the same

2 of 2 pairs shown, highest description similarity first.
Tool	Tool	Description similarity	Name similarity
getNetworkPoolsFilter	filterNetworkTokens	0.73	0.17
getPoolIndicator	getTokenIndicator	0.63	0.50

Tools

getTokenDetails

75 / 100Clear

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 22 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

getNetworkDexes

77 / 100Clear

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 24 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

getNetworkPools

77 / 100Clear

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 24 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

getTokenIndicator

77 / 100Clear

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 22 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Its description is nearly the same as getPoolIndicator's (similarity 0.63); only the names and schemas tell them apart. Say in this description when to use getPoolIndicator instead.confusable_pair

getStats

78 / 100Clear

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 25 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

filterNetworkTokens

81 / 100Clear

Purpose: 20 / 20
When to use: 10 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Minor
Its description is nearly the same as getNetworkPoolsFilter's (similarity 0.73); only the names and schemas tell them apart. Say in this description when to use getNetworkPoolsFilter instead.confusable_pair

getNetworkPoolsFilter

81 / 100Clear

Purpose: 20 / 20
When to use: 10 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Minor
Its description is nearly the same as filterNetworkTokens's (similarity 0.73); only the names and schemas tell them apart. Say in this description when to use filterNetworkTokens instead.confusable_pair

getPoolDetails

82 / 100Clear

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 22 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

getTokenOHLCV

82 / 100Clear

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 22 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

getTokenPools

82 / 100Clear

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 22 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

getTokenMultiPrices

85 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 22 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

getTopTokens

87 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 24 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

submitFeedback

87 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 25 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

No issues.

getCapabilities

90 / 100Clear

Purpose: 20 / 20
When to use: 10 / 20
Arguments: 25 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

getPoolTransactions

91 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 21 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

search

92 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 22 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

getDexPools

93 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 23 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

getNetworks

95 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 25 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

getPoolIndicator

97 / 100Clear

Purpose: 20 / 20
When to use: 20 / 20
Arguments: 22 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Minor
Its description is nearly the same as getTokenIndicator's (similarity 0.63); only the names and schemas tell them apart. Say in this description when to use getTokenIndicator instead.confusable_pair

getPoolOHLCV

97 / 100Clear

Purpose: 20 / 20
When to use: 20 / 20
Arguments: 22 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

What static scoring cannot tell

This score reads only the text of each description and schema: it says what is written, not what a model will do. Short tools whose names already say what they do, such as browser_close, score low here even when models use them well, and in our measurements current models chose the right tool in one step even from one-line descriptions, as long as the names and schemas differed. What the text cannot show, such as what happens over several steps and whether an added sentence helps or misleads, is what an evaluation measures, on the Pro and Team plans.

Is your server listed here and you would rather it were not? Email support@forecall.dev, and we will take it off within 7 days.

All scored servers