Skip to main content
Glama

Base token price

base_token_price
Read-onlyIdempotent

Executable Base token USD price from simulated trade, FDV, liquidity and sellability. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, sign with your own wallet, call again with payment.

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": {
      "token": "<token>"
    },
    "name": "base_token_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesBase ERC20 token contract address (0x...)
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely new behavior: a $0.003 per-call charge, accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the two-step sign-then-pay handshake. What it omits is the shape or freshness of the returned price.

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?

Three tight sentences, front-loaded with what the price is and how it is derived, then cost, then the call sequence. No filler, though the payment-rail parenthetical is dense and could be shortened without loss.

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?

With no output schema, the description should say what a successful call returns; it only implies a single USD price while also referencing FDV, liquidity and sellability, leaving the response shape ambiguous. For a two-parameter read-only tool the invocation side is complete, but the result side is under-described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: it explains that `payment` is optional on the first call and becomes required only after the caller signs the returned terms. That sequencing is not derivable from the schema's one-line parameter note.

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 uses a specific verb+resource framing: an 'executable Base token USD price' computed 'from simulated trade, FDV, liquidity and sellability'. That distinguishes it in substance from a generic spot-price tool like crypto_price, though it never names a sibling explicitly.

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?

It gives clear invocation guidance for the payment flow (call once without `payment` to get terms, sign with your own wallet, call again with `payment`), but says nothing about when to choose this over the price or verdict siblings. The workflow guidance is present; the alternative-selection guidance is not.

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