Skip to main content
Glama

AgentHC Market Intelligence

get_crypto_data

Crypto market data: prices, dominance, sentiment, and cycle analysis.

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": "get_crypto_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoResponse format. 'agent' returns actionable signals, urgency, delta tracking, and suggested follow-ups.full
include_promptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / format
      Added value: +{
      +  "default": "full",
      +  "description": "Response format. 'agent' returns actionable signals, urgency, delta tracking, and suggested follow-ups.",
      +  "enum": [
      +    "full",
      +    "compact",
      +    "prompt",
      +    "agent"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and gives almost nothing: no data freshness/latency, no caching, no auth or rate-limit notes, and no indication of what the 'cycle analysis' or 'sentiment' components compute. Calling this tool blind is risky given the only behavioral hints live in the schema's enum description, not here.

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?

A single twelve-word sentence with no filler and no hedging — front-loaded and easy to ingest. It earns its brevity, though the terseness is achieved by omission rather than by careful compression.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Four response formats including an 'agent' mode with signals and follow-ups, plus a prompt-inclusion flag, but no output schema and no annotations means the description must explain payload shape and the effect of the flags. Instead it lists data categories and stops, leaving an agent unable to predict what it will receive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description says nothing about either parameter. At 50% schema coverage, `format` is documented in the schema but `include_prompt` is undocumented in both places, and the description does not explain when to pick 'compact' vs 'agent' or what including a prompt costs. It fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Crypto market data: prices, dominance, sentiment, and cycle analysis" names the resource and enumerates the data categories returned, but as a bare noun phrase it has no verb and no diffentiation from siblings like get_market_snapshot or get_news_sentiment, which plausibly overlap on prices and sentiment. An agent can infer the domain but not the exact boundary.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of the sibling tools that look competitive (market snapshot, news sentiment). Nothing tells an agent whether this is the right call for 'current BTC price' versus a snapshot or a sentiment-specific tool.

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