Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_nfts_market_chart

Read-only

Retrieve historical market data for NFT collections, including floor price, market cap, and 24-hour volume over specified time periods.

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 query historical market data of a NFT collection, including floor price, market cap, and 24hr volume, by number of days away from now

Response Schema

{
  $ref: '#/$defs/market_chart_get_response',
  $defs: {
    market_chart_get_response: {
      type: 'object',
      properties: {
        floor_price_native: {
          type: 'array',
          description: 'NFT collection floor price in native currency',
          items: {
            type: 'array',
            items: {
              type: 'number'
            }
          }
        },
        floor_price_usd: {
          type: 'array',
          description: 'NFT collection floor price in usd',
          items: {
            type: 'array',
            items: {
              type: 'number'
            }
          }
        },
        h24_volume_native: {
          type: 'array',
          description: 'NFT collection volume in 24 hours in native currency',
          items: {
            type: 'array',
            items: {
              type: 'number'
            }
          }
        },
        h24_volume_usd: {
          type: 'array',
          description: 'NFT collection volume in 24 hours in usd',
          items: {
            type: 'array',
            items: {
              type: 'number'
            }
          }
        },
        market_cap_native: {
          type: 'array',
          description: 'NFT collection market cap in native currency',
          items: {
            type: 'array',
            items: {
              type: 'number'
            }
          }
        },
        market_cap_usd: {
          type: 'array',
          description: 'NFT collection market cap in usd',
          items: {
            type: 'array',
            items: {
              type: 'number'
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
daysYesdata up to number of days Valid values: any integer or max
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 annotation 'readOnlyHint: true' already indicates this is a safe read operation. The description adds value by emphasizing performance optimization with 'jq_filter' and specifying the data types returned (floor price, market cap, volume in native/USD). However, it doesn't disclose other behavioral traits like rate limits, authentication needs, or pagination behavior, leaving some gaps despite the annotation covering the safety aspect.

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 moderately concise but has structural issues. The first two sentences focus on 'jq_filter' usage, which is helpful but front-loads parameter advice over core purpose. The third sentence states the tool's purpose clearly. However, the inclusion of a full output schema in the description text is redundant and verbose, as context signals indicate 'Has output schema: false', but this embedded schema adds unnecessary length without being part of the structured output schema field.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 parameters, historical data query), the description is fairly complete. It covers the tool's purpose, key parameters, and performance tips, and the embedded output schema provides detailed return value information (though redundantly). With annotations indicating read-only safety and good parameter coverage, the main gap is lack of sibling differentiation, but overall it supports effective agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67%, with 'days' and 'jq_filter' well-documented in the schema. The description adds meaningful context: it explains the purpose of 'jq_filter' for performance and references the output schema for field availability. It also clarifies that 'days' specifies 'number of days away from now' for historical data. This compensates well for the partial schema coverage, though it doesn't detail the 'id' parameter beyond what's implied.

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 historical market data of a NFT collection, including floor price, market cap, and 24hr volume, by number of days away from now.' This specifies the verb ('query'), resource ('historical market data of a NFT collection'), and key data fields. However, it doesn't explicitly differentiate from sibling tools like 'get_range_coins_market_chart' or 'get_markets_nfts', which might offer similar functionality for different asset types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage guidance for the 'jq_filter' parameter ('always use... to reduce response size and improve performance. Only omit if you're sure you don't need the data'), which helps optimize tool invocation. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., 'get_range_coins_market_chart' for coins vs. NFTs), and doesn't mention prerequisites or exclusions beyond the parameter advice.

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