aigroup-finnhub-mcp

finnhub_crypto_data

Retrieve cryptocurrency exchange, symbol, quote, and candlestick data. Export results to JSON for analysis.

Instructions

Access cryptocurrency market data. Supports JSON export for large datasets.. Operations: get_exchanges, get_symbols, get_quote, get_candles

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": {
      "operation": "<operation>"
    },
    "name": "finnhub_crypto_data"
  }
}

Input Schema

Name	Required	Description
`days`	No
`export`	No	Force export to JSON file
`symbol`	No	Crypto symbol
`project`	No	Project name for saving data
`exchange`	No	Crypto exchange name
`operation`	Yes
`resolution`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Jul 5, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It mentions JSON export support, which is a behavioral trait, but lacks details on data freshness, rate limits, or any side effects. The listed operations are present but not explained.

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?

The description is short and front-loaded with the main purpose. It uses two sentences, though there is a grammatical double period and missing space. Overall, it is efficient but could be cleaner.

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 7 parameters, multiple operations, no output schema, and no annotations, the description is incomplete. It does not explain how parameters relate to operations (e.g., get_candles likely needs symbol, exchange, resolution, days) or what data is returned. The agent lacks sufficient context to invoke the tool correctly.

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 57% (4 of 7 parameters have descriptions). The description adds context for the 'export' parameter (JSON export for large datasets) but does not compensate for missing descriptions on 'days', 'operation', and 'resolution'. The operation list is helpful but already in the schema enum.

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 it accesses cryptocurrency market data and lists four operations. This distinguishes it from sibling tools like finnhub_stock_market_data by resource type, though it does not explicitly differentiate from other finnhub crypto-related tools.

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 the many sibling tools. There are no usage triggers, prerequisites, or exclusions mentioned.

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

Deploy Server