Skip to main content
Glama
recallnet

Trading Simulator MCP Server

by recallnet

get_token_info

Retrieve detailed information about a cryptocurrency token, including its address, blockchain type, and specific chain details for EVM tokens.

Instructions

Get detailed information about a token

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesToken address
chainNoOptional blockchain type
specificChainNoOptional specific chain for EVM tokens

Implementation Reference

  • src/index.ts:186-211 (registration)
    Registers the 'get_token_info' tool with the MCP server by defining its name, description, and input schema in the TRADING_SIM_TOOLS array.
    {
      name: "get_token_info",
      description: "Get detailed information about a token",
      inputSchema: {
        type: "object",
        properties: {
          token: {
            type: "string",
            description: "Token address"
          },
          chain: {
            type: "string",
            enum: ["svm", "evm"],
            description: "Optional blockchain type"
          },
          specificChain: {
            type: "string",
            enum: ["eth", "polygon", "bsc", "arbitrum", "base", "optimism", "avalanche", "linea", "svm"],
            description: "Optional specific chain for EVM tokens"
          }
        },
        required: ["token"],
        additionalProperties: false,
        $schema: "http://json-schema.org/draft-07/schema#"
      }
    },
  • MCP server handler for the 'get_token_info' tool: validates input parameters and delegates execution to the tradingClient.getTokenInfo method.
    case "get_token_info": {
      if (!args || typeof args !== "object" || !("token" in args)) {
        throw new Error("Invalid arguments for get_token_info");
      }
      
      const token = args.token as string;
      const chain = "chain" in args ? args.chain as BlockchainType : undefined;
      const specificChain = "specificChain" in args ? args.specificChain as SpecificChain : undefined;
      
      const response = await tradingClient.getTokenInfo(token, chain, specificChain);
      return {
        content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
        isError: false
      };
    }
  • Core implementation of getTokenInfo: constructs API request to /api/price/token-info endpoint with token, chain, and specificChain parameters, and handles the HTTP GET request via the client's request method.
    async getTokenInfo(
      token: string,
      chain?: BlockchainType,
      specificChain?: SpecificChain
    ): Promise<TokenInfoResponse | ErrorResponse> {
      const params = new URLSearchParams();
      params.append('token', token);
      
      if (chain) params.append('chain', chain);
      if (specificChain) params.append('specificChain', specificChain);
      
      return this.request<TokenInfoResponse>(
        'GET', 
        `/api/price/token-info?${params.toString()}`,
        null,
        'get token info'
      );
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but only states what the tool does, not how it behaves. It doesn't mention whether this is a read-only operation, what kind of information is returned, potential rate limits, authentication requirements, or error conditions. For a tool with 3 parameters and no annotation coverage, this is inadequate.

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

Conciseness5/5

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

The description is a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a tool with this level of complexity and front-loads the essential information.

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 has 3 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what 'detailed information' means in terms of return values, doesn't address behavioral aspects like read/write nature or error handling, and provides no context about when to use this versus sibling tools.

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?

With 100% schema description coverage, the input schema already documents all parameters thoroughly. The description doesn't add any meaningful context about parameter usage beyond what's in the schema. The baseline score of 3 reflects adequate but unenhanced parameter documentation.

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 verb 'Get' and the resource 'detailed information about a token', making the purpose immediately understandable. However, it doesn't differentiate this tool from potential siblings like 'get_price' or 'get_balances' that might also provide token-related information, which prevents a perfect 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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_price', 'get_balances', and 'get_portfolio' that might overlap with token information, there's no indication of what makes this tool distinct or when it should be preferred over those other options.

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/recallnet/trading-simulator-mcp'

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