Skip to main content
Glama

Crypto today

crypto_today
Read-onlyIdempotent

Why crypto is up or down today, from StockMap's Crypto today page: Bitcoin's 24-hour move, how many coins beat it, funding, and the hour's paragraph, every number with its source. Market data with no call on any coin. Each answer carries the stamp, the sources and the not-advice line.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crypto_today"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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.8/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral context by noting that every number is sourced, each answer carries a stamp and sources, and a not-advice line is included. It does not contradict the annotations.

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 description is front-loaded and appropriately short for a no-parameter data tool. There is minor redundancy between 'every number with its source' and 'the sources,' but no sentence is wasted.

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?

Given the output schema and annotations, the description is largely complete. It explains what data is returned and the sourcing/disclaimer framing. A small gap is the absence of explicit update cadence or freshness beyond 'today' and 'the hour's paragraph.'

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?

This tool has zero parameters, so the baseline is 4. The description does not need to explain parameter meanings, and the empty input schema is consistent with the tool's no-parameter nature.

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 clearly identifies a specific resource and content set: today's crypto move, Bitcoin's 24-hour move, breadth, funding, and the hourly paragraph. It is more specific than the tool name alone, though it does not explicitly contrast itself with named siblings like crypto_stocks or is_it_altseason.

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 focus on 'why crypto is up or down today' and the boundary 'Market data with no call on any coin.' However, it does not explicitly state when to use this tool versus its crypto-related siblings or name an alternative.

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