Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_new_coins_list

Read-only

Retrieve recently listed cryptocurrencies from CoinGecko to monitor new market entries and identify emerging assets for 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 the latest 200 coins that recently listed on CoinGecko

Response Schema

{
  $ref: '#/$defs/list_get_new_response',
  $defs: {
    list_get_new_response: {
      type: 'array',
      items: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'coin ID'
          },
          activated_at: {
            type: 'number',
            description: 'timestamp when coin was activated on CoinGecko'
          },
          name: {
            type: 'string',
            description: 'coin name'
          },
          symbol: {
            type: 'string',
            description: 'coin symbol'
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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 provide readOnlyHint=true, indicating a safe read operation. The description adds behavioral context by specifying that it returns the 'latest 200 coins' and includes a response schema, which clarifies the output structure. However, it doesn't disclose other traits like rate limits, authentication needs, or pagination behavior. With annotations covering safety, the description adds moderate value, warranting a score of 3.

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 front-loaded with usage advice and purpose, but it includes a verbose response schema that duplicates structured data, reducing efficiency. The first two sentences are valuable, but the schema section could be omitted since there's no output schema field, making it somewhat bloated. It earns a 3 for mixed conciseness.

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 low complexity (1 optional parameter) and annotations covering safety, the description is mostly complete. It explains the purpose, usage, and output format via the embedded schema. However, it lacks details on error handling or limitations like the 200-coin limit's implications, slightly reducing completeness. With no output schema, the included response schema helps, but it's not fully integrated.

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?

The input schema has 100% description coverage for the single parameter 'jq_filter,' detailing its purpose and examples. The description reinforces this by emphasizing its use for performance but doesn't add new semantic details beyond what the schema provides. With high schema coverage, the baseline is 3, as the description doesn't significantly enhance parameter understanding.

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 latest 200 coins that recently listed on CoinGecko.' It specifies the verb 'query' and resource 'coins,' and distinguishes itself from siblings by focusing on newly listed coins rather than other coin data like markets, history, or categories. However, it doesn't explicitly differentiate from tools like 'get_search_trending' or 'get_coins_top_gainers_losers' that might also involve recent activity, making it a 4 instead of a 5.

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: '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 gives explicit when-to-use advice for the parameter. However, it lacks guidance on when to use this tool versus sibling alternatives like 'get_coins_markets' or 'get_search_trending' for similar data needs, preventing a score of 5.

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