Skip to main content
Glama

sol_price

Read-onlyIdempotent

Spot USD price from the deepest DEX pair — Spot USD price for any SPL mint from the deepest DEX pair (DexScreener), with FDV and the number of pairs. No DEX price found → not charged. Not advice. Required input: mint. Priced $0.01 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

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": {
      "mint": "<mint>"
    },
    "name": "sol_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana SPL mint address

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, yet the description adds substantial context beyond them: the data source (deepest DexScreener pair), the returned metrics (FDV, number of pairs), and a full billing model ($0.01/call over x402 on Base, prepaid x-credit-token header for unlimited use, one free call/day, no API key). The no-charge-on-missing-price rule is exactly the kind of behavioral detail annotations cannot express.

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?

Front-loaded with the core purpose and dense with decision-relevant facts, but the opening repeats itself ('Spot USD price from the deepest DEX pair — Spot USD price for any SPL mint from the deepest DEX pair') and the payment terms are packed into one run-on sentence, costing clarity.

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 one-parameter read-only price lookup with an output schema and full annotation coverage, this is close to complete: source, return fields, payment/auth mechanics, and the no-price case are all covered. The only gap is routing versus sibling price tools, which matters given the crowded catalog.

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% for the single 'mint' parameter, so the schema already carries the semantics and the baseline of 3 applies. The description only restates that mint is required and implies it must be an SPL mint address — marginal value added.

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?

States a specific verb+resource: spot USD price for any SPL mint, sourced from the deepest DEX pair on DexScreener, plus FDV and pair count. The scope (Solana SPL mints only) is clear, but it never distinguishes itself from sibling tools like token_price or multi_price, so an agent cannot route on this text alone.

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?

Usage is implied rather than stated: use it to price a single mint. It adds a useful failure-mode note ('No DEX price found → not charged') but gives no explicit when-not guidance or pointer to multi_price for batch lookups, even though that sibling clearly competes.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources