Skip to main content
Glama
Sign In
CoinStats MCP Server

CoinStats MCP Server

Official
by CoinStatsHQ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-coin-chart-by-id

Retrieve cryptocurrency chart data by specifying a coin identifier and time period to analyze price trends and historical performance.

Instructions

Get chart data for a specific cryptocurrency based on its unique identifier, specifying different time ranges.

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": {
      "coinId": "<coinId>",
      "period": "<period>"
    },
    "name": "get-coin-chart-by-id"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinIdYesThe identifier of coin, which you received from /coins call response.
periodYesTime period for chart data

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it 'gets' data, implying a read-only operation, but doesn't clarify authentication needs, rate limits, response format, or error handling. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that front-loads the core purpose. It avoids unnecessary words and directly addresses what the tool does. However, it could be slightly more structured by separating the purpose from the parameter context.

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?

Given no annotations and no output schema, the description is moderately complete for a simple read operation. It covers the purpose and hints at parameters, but lacks details on authentication, response format, or error handling. For a tool with 2 parameters and 100% schema coverage, it's adequate but leaves room for improvement in behavioral context.

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 the schema fully documents both parameters. The description adds minimal value beyond the schema by mentioning 'time ranges' which aligns with the 'period' parameter, but doesn't provide additional context like format examples or usage tips. Baseline 3 is appropriate when schema does the heavy lifting.

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 verb 'Get' and resource 'chart data for a specific cryptocurrency', making the purpose evident. It distinguishes from siblings like 'get-coin-by-id' by specifying chart data retrieval rather than general coin information. However, it doesn't explicitly differentiate from 'get-portfolio-chart' which might serve a similar charting function for portfolios.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get-coin-by-id' for general data or 'get-portfolio-chart' for portfolio-specific charts. It mentions 'specifying different time ranges' but doesn't explain when to choose this over other charting or data retrieval tools in the sibling list.

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