Skip to main content
Glama
Sign In
Universal Crypto MCP

Universal Crypto MCP

by nirholas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

geckoterminal_global_dex_stats

Obtain global decentralized exchange statistics and market overview for informed crypto trading decisions.

Instructions

Get global DEX trading statistics and market overview

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided and the description offers almost no additional behavioral detail. It does not specify what metrics are included, whether the data is real-time, or the return format, leaving the agent to infer behavior from the tool name alone.

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 wasted words. It efficiently conveys the tool's purpose without redundancy.

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

Completeness3/5

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

As a parameterless tool without an output schema, the description gives a high-level purpose but fails to elaborate on the actual contents of 'trading statistics' or 'market overview.' It is minimally sufficient for invocation but not deeply informative.

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?

The tool has zero parameters, so the schema already fully describes its signature. The description's 'global' qualifier adds no parameter-specific meaning, but no compensation is necessary; the baseline of 4 is appropriate.

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 clearly states the tool 'Get global DEX trading statistics and market overview' using a specific verb and resource. The 'global' scope distinguishes it from many geckoterminal siblings that focus on individual pools or networks, though it does not explicitly name alternatives.

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 description implies usage when global DEX statistics are needed, but provides no explicit guidance on when to choose this tool over other stats tools like market_get_global or dex_get_stats. It lacks exclusions or alternative recommendations.

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