openpulsechain

Official

by openpulsechain

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get Token Price

get-token-price

Read-onlyIdempotent

Retrieve current price, 24-hour change, volume, and market cap for any PulseChain token using its contract address.

Instructions

Get current price, 24h change, volume, and market cap for a PulseChain token.

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": {
      "address": "<address>"
    },
    "name": "get-token-price"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Token contract address (0x...) — e.g. 0x2b591e99afe9f32eaa6214f7b7629768c40eeb39 for HEX

Output Schema

Name	Required	Description
`address`	Yes	Token contract address
`price_usd`	Yes	Current price in USD
`price_change_24h`	Yes	24-hour price change percentage
`volume_24h`	Yes	24-hour trading volume in USD
`market_cap`	Yes	Market capitalization in USD

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.3May 1, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating safe reads. The description adds the specific data fields returned, providing behavioral context beyond annotations.

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, well-structured sentence that immediately conveys the tool's purpose with no unnecessary words.

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?

Given the existence of an output schema, the description need not detail return values. It adequately covers the returned metrics and specifies the blockchain (PulseChain). Minor omissions like timezone for 24h change are not critical.

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%, and the schema description already explains the 'address' parameter clearly. The description adds no additional meaning beyond what the schema provides.

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 it retrieves current price, 24h change, volume, and market cap for a PulseChain token. It distinguishes from siblings like get-token-info (general info) and get-token-liquidity (liquidity-specific) by specifying exact metrics.

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?

No explicit guidance on when to use this tool over alternatives. The description implicitly suggests use for price-related queries, but does not mention when to prefer get-token-info or get-market-overview.

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