Skip to main content
Glama
Sign In
bca-mcp

bca-mcp

by blockchainacademics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_ohlc

Retrieve historical OHLC candlestick data for any cryptocurrency token to support technical analysis and backtesting strategies.

Instructions

OHLC candlestick history for a token. Starter tier. Useful for technical-setup agents and backtesting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_ohlc"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCoinGecko id (e.g. 'bitcoin').
daysNoLookback days (1-365).
vsNoQuote currency (default usd).usd

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full burden. It states 'OHLC candlestick history', implying output data, but does not disclose rate limits, data freshness, pagination, or any constraints beyond the schema. It's minimally transparent.

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

Conciseness5/5

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

Extremely concise—two sentences that front-load the core purpose and add a usage hint. Every sentence earns its place with no wasted words.

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 exists, so the description should compensate. It mentions 'OHLC candlestick history' but not the return format, ordering, or any limitations beyond 'Starter tier'. For a simple 3-parameter tool, it's moderately complete but missing key details for an agent to fully interpret results.

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?

Input schema coverage is 100%, so the schema already documents all three parameters (id, days, vs). The description adds no extra parameter information. Baseline of 3 is appropriate.

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 clearly states the tool returns OHLC candlestick history for a token, using a specific verb ('get') and resource ('candlestick history'). It mentions 'Starter tier' which hints at limitations, but does not explicitly distinguish from similar tools like get_history_prices or get_price.

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?

It provides some context ('Starter tier', 'useful for technical-setup agents and backtesting'), but no explicit when-to-use or when-not-to-use, nor alternatives. The guidance is implied rather than explicit.

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

Deploy Server

Other Tools