Skip to main content
Glama
Sign In
Corvus

Corvus

by Allen-Saji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_token_price

Fetches current USD prices for Solana tokens using symbols or mint addresses, returning price and confidence score.

Instructions

Get current prices for one or more Solana tokens. Accepts token symbols (SOL, USDC, JitoSOL, etc.) or mint addresses. Returns price in USD with confidence score. Use this for spot price checks.

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": {
      "tokens": "<tokens>"
    },
    "name": "get_token_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokensYesComma-separated list of token symbols or mint addresses (e.g., 'SOL,USDC,JitoSOL' or mint addresses)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that it returns USD price with confidence score, but lacks detail on error handling, rate limits, or data source. For a simple price query, this is adequate but not thorough.

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?

Two sentences, no unnecessary words. The action is front-loaded and every sentence adds value.

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?

For a simple tool with one parameter and no output schema, the description covers inputs, action, and return value. It could explicitly mention that output is a mapping from token to price/confidence, but the description is sufficient for an agent to understand the tool's purpose and usage.

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 baseline is 3. The description largely repeats the schema's parameter description ('Accepts token symbols or mint addresses'), adding minimal new meaning.

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 ('Get current prices'), the resource ('Solana tokens'), and the output ('price in USD with confidence score'). It distinguishes from siblings like 'get_token_balances' which focuses on balances rather than prices.

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

Usage Guidelines4/5

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

The description explicitly states 'Use this for spot price checks', providing direct usage guidance. It does not explicitly list when not to use, but the sibling context makes alternatives clear. Minor improvement would be to mention that for historical prices a different tool is needed.

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