Skip to main content
Glama
Sign In

SwapChan

by io.github.TSavo
OverviewDiscussionsAdmin

Historical coin price

price_history
Read-only

Past USD price of a coin from DefiLlama (keyless, no key): pass a CoinGecko id ("dogecoin") or a common ticker ("DOGE", "BTC", "ETH", "SOL") and a date, and get the spot price on that day. Add days for a daily trend series from that date forward. This is NOT the live price — use get_quote or token_info for the current price. Use it for questions like "what was DOGE last month". Result includes display markdown: show it to the user. How to combine this with the other tools: swapchan_playbook (workflows: find-money, best-swap, rebalance, revoke-approvals, bridge-stuck, token-safety, recover-old-wallet).

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": {
      "coin": "<coin>",
      "date": "<date>"
    },
    "name": "price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoinGecko id or ticker, e.g. "dogecoin" or "DOGE".
dateYesThe date as YYYY-MM-DD (or an ISO datetime).
daysNoDays of daily trend from the date forward (0 or omit = just that day).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description adds real value by disclosing the data source (DefiLlama), that no API key is required, and that the result carries a `display` markdown field the agent should surface to the user. It doesn't cover failure modes (unknown ticker, out-of-range dates) or rate limits, which keeps it below a 5.

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 core purpose, exclusion, and usage example are front-loaded and tight. The trailing sentence enumerating seven playbook workflows is bolted-on boilerplate that doesn't help an agent call this specific tool, costing it a point.

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?

With no output schema, the description still tells the agent what comes back: a spot price for the date, an optional daily series, and a `display` markdown field to render. That covers the essentials, though the shape of the trend series and error behavior are left implicit.

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 all three parameters are already documented, including ticker examples and the YYYY-MM-DD format. The description largely restates that (id-or-ticker, days = trend forward) rather than adding new semantics; baseline 3 applies.

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?

States a specific verb and resource: past USD spot price of a coin from DefiLlama, keyed by CoinGecko id or ticker plus a date. It explicitly distinguishes itself from the live-price siblings get_quote and token_info, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ("what was DOGE last month"), explicit when-not ("NOT the live price — use get_quote or token_info"), and names the concrete alternatives. The `days` parameter is also framed as an opt-in mode with its own use case.

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

All SwapChan toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources