Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA
OverviewSchemaRelated ServersScoreDiscussions
Hybrid

get_id_nfts

Read-only

Retrieve comprehensive NFT collection data including floor price, 24-hour volume, market cap, and ownership statistics by providing the collection ID.

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 all the NFT data (name, floor price, 24hr volume ...) based on the NFT collection ID

Response Schema

{
  $ref: '#/$defs/nft_get_id_response',
  $defs: {
    nft_get_id_response: {
      type: 'object',
      properties: {
        id: {
          type: 'string',
          description: 'NFT collection ID'
        },
        asset_platform_id: {
          type: 'string',
          description: 'NFT collection asset platform ID'
        },
        ath: {
          type: 'object',
          description: 'NFT collection all time highs',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        ath_change_percentage: {
          type: 'object',
          description: 'NFT collection all time highs change percentage',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        ath_date: {
          type: 'object',
          description: 'NFT collection all time highs date',
          properties: {
            native_currency: {
              type: 'string',
              format: 'date-time'
            },
            usd: {
              type: 'string',
              format: 'date-time'
            }
          }
        },
        banner_image: {
          type: 'object',
          description: 'NFT collection banner image url',
          properties: {
            small: {
              type: 'string'
            }
          }
        },
        contract_address: {
          type: 'string',
          description: 'NFT collection contract address'
        },
        description: {
          type: 'string',
          description: 'NFT collection description'
        },
        explorers: {
          type: 'array',
          description: 'NFT collection block explorers links',
          items: {
            type: 'object',
            properties: {
              link: {
                type: 'string'
              },
              name: {
                type: 'string'
              }
            }
          }
        },
        floor_price: {
          type: 'object',
          description: 'NFT collection floor price',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        floor_price_14d_percentage_change: {
          type: 'object',
          description: 'NFT collection floor price 14 days percentage change',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        floor_price_1y_percentage_change: {
          type: 'object',
          description: 'NFT collection floor price 1 year percentage change',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        floor_price_24h_percentage_change: {
          type: 'object',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        floor_price_30d_percentage_change: {
          type: 'object',
          description: 'NFT collection floor price 30 days percentage change',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        floor_price_60d_percentage_change: {
          type: 'object',
          description: 'NFT collection floor price 60 days percentage change',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        floor_price_7d_percentage_change: {
          type: 'object',
          description: 'NFT collection floor price 7 days percentage change',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        floor_price_in_usd_24h_percentage_change: {
          type: 'number',
          description: 'NFT collection floor price in usd 24 hours percentage change'
        },
        image: {
          type: 'object',
          description: 'NFT collection image url',
          properties: {
            small: {
              type: 'string'
            },
            small_2x: {
              type: 'string'
            }
          }
        },
        links: {
          type: 'object',
          description: 'NFT collection links',
          properties: {
            discord: {
              type: 'string'
            },
            homepage: {
              type: 'string'
            },
            twitter: {
              type: 'string'
            }
          }
        },
        market_cap: {
          type: 'object',
          description: 'NFT collection market cap',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        market_cap_24h_percentage_change: {
          type: 'object',
          description: 'NFT collection market cap 24 hours percentage change',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        market_cap_rank: {
          type: 'number',
          description: 'coin market cap rank'
        },
        name: {
          type: 'string',
          description: 'NFT collection name'
        },
        native_currency: {
          type: 'string',
          description: 'NFT collection native currency'
        },
        native_currency_symbol: {
          type: 'string',
          description: 'NFT collection native currency symbol'
        },
        number_of_unique_addresses: {
          type: 'number',
          description: 'number of unique address owning the NFTs'
        },
        number_of_unique_addresses_24h_percentage_change: {
          type: 'number',
          description: 'number of unique address owning the NFTs 24 hours percentage change'
        },
        one_day_average_sale_price: {
          type: 'number',
          description: 'NFT collection one day average sale price'
        },
        one_day_average_sale_price_24h_percentage_change: {
          type: 'number',
          description: 'NFT collection one day average sale price 24 hours percentage change'
        },
        one_day_sales: {
          type: 'number',
          description: 'NFT collection one day sales'
        },
        one_day_sales_24h_percentage_change: {
          type: 'number',
          description: 'NFT collection one day sales 24 hours percentage change'
        },
        symbol: {
          type: 'string',
          description: 'NFT collection symbol'
        },
        total_supply: {
          type: 'number',
          description: 'NFT collection total supply'
        },
        user_favorites_count: {
          type: 'number',
          description: 'NFT collection user favorites count'
        },
        volume_24h: {
          type: 'object',
          description: 'NFT collection volume in 24 hours',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        volume_24h_percentage_change: {
          type: 'object',
          description: 'NFT collection volume in 24 hours percentage change',
          properties: {
            native_currency: {
              type: 'number'
            },
            usd: {
              type: 'number'
            }
          }
        },
        volume_in_usd_24h_percentage_change: {
          type: 'number',
          description: 'NFT collection volume in usd 24 hours percentage change'
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
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/).

Tool Definition Quality

B3.1/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, which the description does not contradict (it describes a query operation). The description adds behavioral context by advising on performance optimization with 'jq_filter', but does not disclose other traits like rate limits, error handling, or authentication needs. With annotations covering safety, this earns a baseline score for adding some value.

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

Conciseness2/5

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

The description is poorly structured: it starts with a usage tip, then states the purpose, and includes a large, redundant output schema that should be in a separate field. This front-loads non-essential information and wastes space, reducing clarity and efficiency.

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 the tool's complexity (querying NFT data with performance considerations) and lack of output schema (the embedded schema is not properly leveraged), the description is incomplete. It fails to explain return values, error cases, or how the 'jq_filter' interacts with the response structure, leaving significant gaps for agent usage.

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 50% (only 'jq_filter' has a description). The description mentions 'jq_filter' for reducing response size, adding marginal semantics beyond the schema. However, it does not explain the 'id' parameter's format or constraints, leaving half the parameters inadequately documented. Baseline 3 is appropriate given partial compensation.

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 all the NFT data (name, floor price, 24hr volume ...) based on the NFT collection ID'. It specifies the verb ('query'), resource ('NFT data'), and scope ('based on the NFT collection ID'), but does not explicitly differentiate from sibling tools like 'get_list_nfts' or 'get_markets_nfts', which prevents a score of 5.

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 implied usage guidance by emphasizing the 'jq_filter' parameter for performance and stating 'Only omit if you're sure you don't need the data'. However, it lacks explicit when-to-use rules, alternatives (e.g., vs. 'get_list_nfts'), or prerequisites, leaving gaps in agent decision-making.

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