Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_coins_history

Read-only

Retrieve historical cryptocurrency data including price, market cap, and volume for a specific coin on a given date.

Instructions

When using this tool, always use the jq_filter parameter to reduce the response size and improve performance.

Only omit if you're sure you don't need the data.

This endpoint allows you to query the historical data (price, market cap, 24hrs volume, ...) at a given date for a coin based on a particular coin ID

Response Schema

{
  $ref: '#/$defs/history_get_response',
  $defs: {
    history_get_response: {
      type: 'object',
      properties: {
        id: {
          type: 'string',
          description: 'coin ID'
        },
        community_data: {
          type: 'object',
          description: 'coin community data',
          properties: {
            facebook_likes: {
              type: 'number',
              description: 'coin facebook likes'
            },
            reddit_accounts_active_48h: {
              type: 'number',
              description: 'coin reddit accounts active 48h'
            },
            reddit_average_comments_48h: {
              type: 'number',
              description: 'coin reddit average comments 48h'
            },
            reddit_average_posts_48h: {
              type: 'number',
              description: 'coin reddit average posts 48h'
            },
            reddit_subscribers: {
              type: 'number',
              description: 'coin reddit subscribers'
            }
          }
        },
        developer_data: {
          type: 'object',
          description: 'coin developer data',
          properties: {
            closed_issues: {
              type: 'number',
              description: 'coin repository closed issues'
            },
            code_additions_deletions_4_weeks: {
              type: 'object',
              description: 'coin code additions deletions 4 weeks',
              properties: {
                additions: {
                  type: 'number'
                },
                deletions: {
                  type: 'number'
                }
              }
            },
            commit_count_4_weeks: {
              type: 'number',
              description: 'coin commit count 4 weeks'
            },
            forks: {
              type: 'number',
              description: 'coin repository forks'
            },
            pull_request_contributors: {
              type: 'number',
              description: 'coin repository pull request contributors'
            },
            pull_requests_merged: {
              type: 'number',
              description: 'coin repository pull requests merged'
            },
            stars: {
              type: 'number',
              description: 'coin repository stars'
            },
            subscribers: {
              type: 'number',
              description: 'coin repository subscribers'
            },
            total_issues: {
              type: 'number',
              description: 'coin repository total issues'
            }
          }
        },
        image: {
          type: 'object',
          description: 'coin image url',
          properties: {
            small: {
              type: 'string'
            },
            thumb: {
              type: 'string'
            }
          }
        },
        localization: {
          type: 'object',
          description: 'coin localization',
          additionalProperties: true
        },
        market_data: {
          type: 'object',
          description: 'coin market data',
          properties: {
            current_price: {
              type: 'object',
              description: 'coin current price',
              properties: {
                btc: {
                  type: 'number'
                },
                eur: {
                  type: 'number'
                },
                usd: {
                  type: 'number'
                }
              }
            },
            market_cap: {
              type: 'object',
              description: 'coin market cap',
              properties: {
                btc: {
                  type: 'number'
                },
                eur: {
                  type: 'number'
                },
                usd: {
                  type: 'number'
                }
              }
            },
            total_volume: {
              type: 'object',
              description: 'coin total volume',
              properties: {
                btc: {
                  type: 'number'
                },
                eur: {
                  type: 'number'
                },
                usd: {
                  type: 'number'
                }
              }
            }
          }
        },
        name: {
          type: 'string',
          description: 'coin name'
        },
        public_interest_stats: {
          type: 'object',
          description: 'coin public interest stats',
          properties: {
            alexa_rank: {
              type: 'number',
              description: 'coin alexa rank'
            },
            bing_matches: {
              type: 'number',
              description: 'coin bing matches'
            }
          }
        },
        symbol: {
          type: 'string',
          description: 'coin symbol'
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
dateYesdate of data snapshot (`YYYY-MM-DD`)
localizationNoinclude all the localized languages in response, default: true
jq_filterNoA jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available. For example: to include only the `name` field in every object of a results array, you can provide ".results[].name". For more information, see the [jq documentation](https://jqlang.org/manual/).
Behavior3/5

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

The annotations indicate readOnlyHint=true, which the description aligns with by describing a query operation (no contradiction). The description adds behavioral context by highlighting performance considerations with 'jq_filter' and specifying that it returns data 'at a given date,' which clarifies the snapshot nature. However, it doesn't disclose other traits like rate limits, error conditions, or pagination, leaving gaps despite the annotation covering safety.

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 relatively concise, with two sentences upfront about 'jq_filter' usage and the core purpose, followed by an output schema. The front-loaded sentences are efficient, but the inclusion of the full output schema in the description text adds bulk that might be redundant if structured elsewhere. Overall, it's well-structured but could be more streamlined by omitting the schema duplication.

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 the tool's complexity (historical data query with 4 params), annotations cover read-only safety, and schema coverage is high (75%), the description is moderately complete. It explains the purpose and a key performance tip but lacks details on output format (though the embedded schema helps), error handling, or comparisons to siblings. The output schema in the description compensates partially, but it's verbose and might be better handled separately.

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 75%, with parameters 'id' and 'date' well-documented in the schema (e.g., date format 'YYYY-MM-DD'), and 'jq_filter' has a detailed schema description. The description adds minimal param semantics beyond the schema, only emphasizing 'jq_filter' for performance. It doesn't explain 'localization' or provide examples beyond what's in the schema, so it meets the baseline for high schema coverage without significant added value.

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's purpose: 'query the historical data (price, market cap, 24hrs volume, ...) at a given date for a coin based on a particular coin ID.' This specifies the verb ('query'), resource ('historical data'), and scope ('coin ID', 'date'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'get_range_coins_market_chart' or 'get_coins_markets', which might also involve historical or market data.

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?

The description provides some usage guidance by emphasizing the importance of the 'jq_filter' parameter to reduce response size and improve performance, with a note to omit it only if unnecessary. This implies a best practice for when to use this parameter. However, it lacks explicit guidance on when to choose this tool over alternatives (e.g., vs. 'get_coins_markets' for current data or 'get_range_coins_market_chart' for time series), and no prerequisites or exclusions are mentioned.

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/IAcomunIA/MCP_firts'

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