Skip to main content
Glama

Is it altseason?

is_it_altseason
Read-onlyIdempotent

Is it altseason: how many of the top-100 coins (stablecoins out) beat Bitcoin over the last 7 days, beside how many lag it in a typical week, from StockMap's Altseason page. 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": "is_it_altseason"
  }
}

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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: it is market data only, makes no recommendation on any coin, and every answer carries a timestamp, its sources, and a not-advice line — the provenance and disclaimer framing is not in 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?

Three front-loaded sentences that each carry information: the metric, the no-recommendation stance, and the answer payload. The middle clause ('beside how many lag it in a typical week') is slightly awkwardly phrased for what is essentially a comparative baseline, costing a little clarity for its compactness.

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 and zero parameters, the description only needs to establish scope and stance, which it does. The one residual ambiguity is where the 'typical week' benchmark comes from, but that is arguably answered by the output schema and the stated source.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a no-argument call by describing the metric as fixed (top-100, 7 days).

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 computation: the share of top-100 coins (stablecoins excluded) that beat Bitcoin over 7 days, benchmarked against a typical week, from StockMap's Altseason page. The scope (universe, exclusion, timeframe, baseline) is precise enough to separate it from siblings like crypto_today or market_map without opening either schema, and 'no call on any coin' distinguishes it from stock_call.

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?

The altseason framing implies when to reach for it, and naming the data source ('StockMap's Altseason page') gives context, but there is no explicit when-to-use/when-not statement or named alternative. A sibling such as crypto_today could plausibly be chosen instead, and the description doesn't adjudicate that choice.

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