Skip to main content
Glama
CC3-0

CoinCap MCP Server

by CC3-0

ta_slug_macd

Compute the full MACD series for any cryptocurrency asset by specifying slug, timeframe, and EMA periods to obtain MACD line, signal line, and histogram.

Instructions

Full MACD series

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesAsset slug (e.g. bitcoin)
startNoStart timestamp in ms
endNoEnd timestamp in ms
shortNoShort EMA period (default: 12)
longNoLong EMA period (default: 26)
signalNoSignal line EMA period (default: 9)
fetchIntervalNoTimeframe for price bars
includeOriginalNoInclude original price data
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral traits. It fails to disclose computational load, data sources, or any side effects. The phrase 'Full MACD series' is too vague to inform about rate limits, required permissions, or performance characteristics.

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?

The description is excessively short (3 words). While concise, it sacrifices necessary detail. There is no structure or front-loading of key information.

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?

Given the complexity (8 parameters, no output schema), the description is insufficient. It does not explain the return format or how this tool fits into the broader family of indicator tools.

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 description coverage is 100%, so all parameters have descriptions in the schema. The description adds no additional meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 'Full MACD series' clearly indicates it returns the complete MACD indicator series for an asset. It differentiates from sibling tool 'ta_slug_macd_latest' which presumably 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 is provided on when to use this tool versus alternatives like ta_slug_macd_latest or other indicators. The description lacks context about preferred use cases.

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