Skip to main content
Glama

Crypto stocks

crypto_stocks
Read-onlyIdempotent

Which US crypto stocks StockMap's model leans on: how many it leans outperform, neutral or underperform, how many of its graded two-week windows on them were right, and Bitcoin's move since the last US close. The calls are the stock model's, on the stocks, never on coins. 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_stocks"
  }
}

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.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds that every answer carries a stamp, sources, and a not-advice line, which is useful output context but partly redundant given an output schema exists. No disclosure of data freshness beyond 'since the last US close' or rate/latency behavior.

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 sentences, front-loaded with the resource and the returned metrics, with no filler. The first sentence is long and clause-heavy, which slightly slows parsing of the three distinct metrics, but every sentence carries meaning.

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?

It is a zero-parameter, read-only retrieval tool with an output schema and full annotation coverage, so the description's job is mainly to signal what data comes back — which it does. The remaining gap is the absence of routing guidance versus closely related siblings like crypto_today and compare_stocks.

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 the baseline is 4. There is no parameter surface the description needs to explain, and it correctly implies a parameterless snapshot query.

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 names a specific resource (US crypto stocks covered by StockMap's model) and enumerates the content returned: lean counts, hit rate on graded two-week windows, and Bitcoin's move since the last close. It also draws a clear boundary ('the calls are on the stocks, never on coins'), which separates it from crypto_today and bitcoin_test, though the returning verb is implied rather than stated.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the many siblings (stock_call, compare_stocks, crypto_today). The 'never on coins' line gives implicit scope guidance, but the agent must infer that this tool is the right pick for crypto-exposure questions rather than being told.

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