Skip to main content
Glama

Did my coins beat Bitcoin?

bitcoin_test
Read-onlyIdempotent

Did the person's coins beat Bitcoin: their holdings as they would paste them on StockMap's Bitcoin test page ("ETH 2, SOL 40 since Jan 15"), priced then and now beside the same dollars held in Bitcoin, from CoinGecko's prices. Nothing is stored. Arithmetic on past prices: no call on any coin, and no advice on the holdings. Each answer carries the stamp, the sources and the not-advice line.

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": {
      "holdings": "<holdings>"
    },
    "name": "bitcoin_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoWhen they bought, for holdings the paste gives no date (the page's "Held since"), YYYY-MM-DD
holdingsYesThe coins and amounts as the person would paste them, with a date if they gave one: "ETH 2, SOL 40, DOGE 10000 since Jan 15"

Output Schema

NameRequiredDescriptionDefault
cardNoThe page's share card data, with its image URLs (C-1b)
as_ofNoThe feed's time, ISO 8601 UTC
staleYesTrue when the feed is behind: the page shows the same numbers under a banner
stampYesWhen the numbers are from, as the page stamps them; two clocks give two stamps
numbersYesThe page's tiles
page_urlYes
questionYes
sentencesYes
not_adviceNoWe don't tell you what to buy. Research and education, not investment advice.
answer_textYesThe page's own sentences, joined
source_namesYes
stale_reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / not_advice / default
      Previous value: -"We don't tell you what to buy. We show what the data says, and we post receipts. NFA."New value: +"We don't tell you what to buy. Research and education, not investment advice."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower, yet the description still adds meaningful context: pricing source (CoinGecko), that nothing is stored, and that answers include a timestamp, sources and a not-advice disclaimer. It also pre-empts expectations by saying the tool performs arithmetic only and gives no buy/sell call.

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?

Dense but purposeful: the comparison logic comes first, then the non-storage/source/disclaimer guarantees. Sentences are long with nested parentheses, but nothing is redundant filler.

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 an output schema present, return values need not be explained, and the description still mentions the stamp, sources and disclaimer that accompany results. Combined with full annotation coverage and 100% schema coverage, an agent has enough to call this correctly; only sibling routing is unaddressed.

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 the schema already documents both parameters in detail, including the 'Held since' fallback. The description reinforces the paste format with an example, but that example largely duplicates the schema's own holdings example, so added value is marginal.

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 states a concrete operation: price a pasted holdings list at a past date and now, and compare it against the same dollars held in Bitcoin, using CoinGecko prices. That distinguishes it from siblings like compare_stocks (equities) and crypto_today (current prices). The opening clause echoes the title, but the rest of the sentence carries real specificity.

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 by the StockMap Bitcoin test page framing and the paste format, so an agent can infer the intended input. However, no sibling is named and there is no explicit when-not guidance (e.g. versus compare_stocks for multi-asset comparisons or crypto_today for spot prices).

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