Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_list_nfts

Read-only

Query all supported NFT collections on CoinGecko to retrieve IDs, contract addresses, names, asset platforms, and symbols for cryptocurrency analysis.

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 supported NFTs with ID, contract address, name, asset platform ID and symbol on CoinGecko

Response Schema

{
  $ref: '#/$defs/nft_get_list_response',
  $defs: {
    nft_get_list_response: {
      type: 'object',
      properties: {
        id: {
          type: 'string',
          description: 'NFT collection ID'
        },
        asset_platform_id: {
          type: 'string',
          description: 'NFT collection asset platform ID'
        },
        contract_address: {
          type: 'string',
          description: 'NFT collection contract address'
        },
        name: {
          type: 'string',
          description: 'NFT collection name'
        },
        symbol: {
          type: 'string',
          description: 'NFT collection symbol'
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderNouse this to sort the order of responses
pageNopage through results
per_pageNototal results per page Valid values: 1...250
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?

Annotations provide readOnlyHint=true, indicating this is a safe read operation. The description adds behavioral context about performance optimization through jq_filter usage and clarifies the scope of data returned (all supported NFTs with specific fields). However, it doesn't mention pagination behavior, rate limits, authentication needs, or error conditions beyond what annotations cover.

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 appropriately sized with three sentences that each serve a purpose: performance guidance, conditional omission advice, and core functionality explanation. It's front-loaded with the most important usage recommendation. The inclusion of the response schema in the description text adds length but provides necessary context since there's no separate output schema.

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 moderate complexity (4 parameters, read-only operation) and 100% schema coverage, the description is reasonably complete. It includes the response schema directly in the description to compensate for the lack of a separate output schema. The performance guidance and field specification provide adequate context for an agent to use the tool effectively, though sibling tool differentiation is lacking.

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%, with all parameters well-documented in the input schema. The description adds value by emphasizing the importance of the jq_filter parameter for performance and providing a brief example of its usage. However, it doesn't explain the semantics of other parameters like 'order' enum values or 'per_page' range beyond what's already in the schema.

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 supported NFTs with ID, contract address, name, asset platform ID and symbol on CoinGecko'. It specifies the verb 'query' and resource 'NFTs', listing the specific fields returned. However, it doesn't explicitly differentiate from sibling tools like 'get_id_nfts' or 'get_markets_nfts', which might offer different NFT-related functionality.

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 strongly recommending use of the 'jq_filter' parameter to reduce response size and improve performance, with a conditional 'Only omit if you're sure you don't need the data'. However, it doesn't explicitly state when to use this tool versus alternatives among the many NFT-related sibling tools, nor does it mention prerequisites or exclusions.

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