Skip to main content
Glama
Sign In
HyperEVM MCP

HyperEVM MCP

by PlayAINetwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

getTokenDetails

Retrieve token price, market data, and trading metrics from DexScreener API to evaluate a token's trading activity and market position.

Instructions

Fetch comprehensive token details including price, market data, and trading metrics from DexScreener API

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

Input Schema

NameRequiredDescriptionDefault
tokenAddressYesContract address of the token to fetch details for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It states fetching from DexScreener API, implying read-only behavior, but fails to disclose potential behavioral traits like rate limits, authentication needs, error handling, or data freshness.

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?

Single sentence is concise and zero waste. However, no structural elements (e.g., bullet points) are used, though not necessary for this simplicity.

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?

Given the tool has one parameter and no output schema, the description provides a partial picture of outputs (price, market data, trading metrics) but lacks details on return format, error conditions, or data coverage.

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%, so baseline is 3. The description adds no additional meaning beyond the schema's description of tokenAddress.

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 action (Fetch), the resource (comprehensive token details), and the source (DexScreener API). It distinguishes from sibling tools which are DeFi actions or account state queries.

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 use for fetching token market data, but does not explicitly state when to use this tool over alternatives or provide any exclusions. Context from sibling names helps, but the description itself lacks guidance.

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