Skip to main content
Glama
CC3-0

CoinCap MCP Server

by CC3-0

ta_slug_rsi

Retrieve the full RSI series for a cryptocurrency asset. Customize period, smoothing, and time interval to generate historical RSI data, optionally including original prices.

Instructions

Full RSI series

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesAsset slug (e.g. bitcoin)
startNoStart timestamp in ms
endNoEnd timestamp in ms
periodNoRSI calculation period (default: 5)
smoothingNoSmoothing method (default: EMA)
fetchIntervalNoTimeframe for price bars
includeOriginalNoInclude original price data
Behavior2/5

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

No annotations provided. Description does not disclose that this is a read-only computation tool, nor any side effects or data requirements beyond what is implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise (two words), but at the cost of completeness. It is front-loaded but lacks explanatory value.

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?

With 7 parameters and no output schema, description should explain the full series output, time range handling, or defaults. Does not provide sufficient context for correct usage.

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?

Schema coverage is 100%, so baseline is 3. Description adds no additional meaning beyond parameter names and schema descriptions.

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?

Description specifies verb ('Full series') and resource ('RSI'), distinguishing it from siblings like ta_slug_rsi_latest which returns only the latest value.

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 guidance on when to use full series vs other TA tools or alternatives. Does not mention context like data availability or prerequisites.

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/CC3-0/coincap-mcp-server'

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