Skip to main content
Glama
Sign In
Moralis MCP Server

Moralis MCP Server

Official
by MoralisWeb3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

solana_gettokenprice

Retrieve current token prices in USD and native currency by providing a contract address and network on Solana blockchain.

Instructions

Gets the token price (usd and native) for a given contract address and network.

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": {
      "network": "<network>",
      "address": "<address>"
    },
    "name": "solana_gettokenprice"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkYesThe network to query
addressYesThe address to query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It doesn't mention rate limits, authentication requirements, data freshness, error conditions, or response format. 'Gets' implies a read-only operation, but this isn't explicitly stated.

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?

The description is a single, efficient sentence that front-loads the core functionality. Every word contributes to understanding the tool's purpose without unnecessary elaboration.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the return values look like (structure of USD/native prices), potential limitations, or how it differs from similar tools in the server, leaving significant gaps for agent understanding.

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 description coverage is 100%, so parameters are fully documented in the schema. The description adds minimal value by mentioning 'contract address and network' but doesn't clarify parameter relationships or provide examples beyond what the schema already specifies.

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 action ('Gets') and resource ('token price'), specifying both USD and native currency outputs. It distinguishes itself from sibling tools like 'solana_getmultipletokenprices' by focusing on a single token, though it doesn't explicitly mention this distinction.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'solana_getmultipletokenprices' for batch queries or 'evm_gettokenprices' for EVM networks. The description only states what it does, not when it's appropriate.

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