Skip to main content
Glama

get-historical-analysis

Retrieve historical cryptocurrency price analysis with customizable time intervals and duration to identify market trends and patterns.

Instructions

Get historical price analysis with customizable timeframe

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesCryptocurrency symbol (e.g., BTC, ETH)
intervalNoTime interval (m5, m15, m30, h1, h2, h6, h12, d1)h1
daysNoNumber of days to analyze (1-30)
Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as data source (e.g., real-time vs delayed), caching, rate limits, or whether the analysis includes derived metrics like moving averages.

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?

Single sentence, front-loaded with action and key qualifier. No wasted words, but could benefit from a second sentence to enhance completeness without harming conciseness.

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

Completeness3/5

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

No output schema, so the agent cannot infer return format or fields. Description lacks details on data scope (e.g., OHLCV, volume) and pagination. Adequate for a simple analysis tool but incomplete.

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?

With 100% schema coverage, parameters are documented. The description adds 'customizable timeframe' but does not elaborate on default behavior or mutually exclusive options beyond schema.

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?

The description clearly states the tool retrieves historical price analysis with customizable timeframe. It distinguishes from 'get-crypto-price' (current price) and 'get-market-analysis' (broader market).

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?

No explicit guidance on when to use this tool versus siblings. The description does not specify context like trend analysis vs point-in-time price, nor any prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wazzan/mcp-coincap-jj'

If you have feedback or need assistance with the MCP directory API, please join our Discord server