Skip to main content
Glama

exchangeMap

Retrieve mapping of cryptocurrency exchanges to CoinMarketCap IDs for data integration and querying.

Instructions

Returns a mapping of all exchanges to unique CoinMarketCap IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listing_statusNo
slugNo
startNo
limitNo
sortNo

Implementation Reference

  • index.js:469-485 (registration)
    Registration of the 'exchangeMap' tool on the MCP server, including its description and input schema.
    // /exchange/map
    server.tool("exchangeMap",
      "Returns a mapping of all exchanges to unique CoinMarketCap IDs.",
      {
        listing_status: z.string().optional(),
        slug: z.string().optional(),
        start: z.number().optional(),
        limit: z.number().optional(),
        sort: z.string().optional()
      },
      async (params) => {
        return handleEndpoint(async () => {
          const data = await makeApiRequest(apiKey, '/v1/exchange/map', params)
          return formatResponse(data)
        })
      }
    )
  • The handler function that executes when 'exchangeMap' is called. It makes an API request to '/v1/exchange/map' and formats the response.
      async (params) => {
        return handleEndpoint(async () => {
          const data = await makeApiRequest(apiKey, '/v1/exchange/map', params)
          return formatResponse(data)
        })
      }
    )
  • Input schema for the 'exchangeMap' tool using Zod, defining optional parameters: listing_status, slug, start, limit, sort.
    {
      listing_status: z.string().optional(),
      slug: z.string().optional(),
      start: z.number().optional(),
      limit: z.number().optional(),
      sort: z.string().optional()
    },
  • The handleEndpoint helper function that wraps the API call with error handling, used by the exchangeMap handler.
    async function handleEndpoint(apiCall) {
      try {
        return await apiCall()
      } catch (error) {
        return formatErrorResponse(error.message, error.status || 403)
      }
    }
Behavior2/5

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

With no annotations, the description carries the full burden. It only mentions output (mapping) but fails to disclose any behavioral traits like pagination, filtering, rate limits, or authentication needs. Minimal behavioral insight.

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 a single concise sentence with no waste, but it is overly brief to the point of being insufficient. It lacks necessary detail for a tool with 5 parameters.

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

Completeness1/5

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

Given the schema has 5 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the return value structure is, how parameters affect results, or any usage constraints.

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

Parameters1/5

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

Schema description coverage is 0% across 5 parameters. The description does not explain any parameter (listing_status, slug, start, limit, sort), leaving the agent to guess their meaning and usage.

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 it returns a mapping of exchanges to CoinMarketCap IDs, which is a specific verb and resource. However, it does not differentiate it from sibling tools like exchangeAssets or exchangeInfo, preventing a top score.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor any context about prerequisites or exclusions. The description only states what it does, not when to choose it.

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/shinzo-labs/coinmarketcap-mcp'

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