Skip to main content
Glama
Jake-loranger

Algorand MCP Server

get_asset_info

Retrieve detailed information about Algorand Standard Assets by providing the asset ID, enabling users to verify asset properties and metadata on the blockchain.

Instructions

Get information about an Algorand Standard Asset

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetIdYesAsset ID to query

Implementation Reference

  • MCP tool handler for 'get_asset_info' that parses arguments, calls algorandService.getAssetInfo, and formats the response or error.
    case 'get_asset_info': {
        const parsed = GetAssetInfoArgsSchema.parse(args);
        try {
            const assetInfo = await algorandService.getAssetInfo(parsed.assetId);
            return {
                content: [
                    {
                        type: 'text',
                        text: `Asset Information:\n${JSON.stringify(assetInfo, null, 2)}`,
                    },
                ],
            };
        } catch (error) {
            return {
                content: [
                    {
                        type: 'text',
                        text: `Error getting asset info: ${error}`,
                    },
                ],
                isError: true,
            };
        }
    }
  • Zod schema for validating input arguments to the get_asset_info tool (assetId: number).
    const GetAssetInfoArgsSchema = z.object({
        assetId: z.number(),
    });
  • src/index.ts:295-308 (registration)
    Tool registration in the TOOLS array, defining name, description, and inputSchema for MCP server.
    {
        name: 'get_asset_info',
        description: 'Get information about an Algorand Standard Asset',
        inputSchema: {
            type: 'object',
            properties: {
                assetId: {
                    type: 'number',
                    description: 'Asset ID to query',
                },
            },
            required: ['assetId'],
        },
    },
  • Core implementation in AlgorandService class that queries the algod client for asset information by ID.
    async getAssetInfo(assetId: number) {
        try {
            const assetInfo = await this.algodClient.getAssetByID(assetId).do();
            return {
                id: assetInfo.index,
                params: assetInfo.params,
            };
        } catch (error) {
            throw new Error(`Failed to get asset info: ${error}`);
        }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Get information') but does not describe traits like whether it's read-only, requires authentication, has rate limits, or what the return format includes. This leaves significant gaps for a tool that likely queries blockchain data.

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, direct sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration.

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 lack of annotations and output schema, the description is insufficient for a tool that likely returns detailed asset information. It does not explain what data is returned (e.g., metadata, supply, creator) or handle complexities like error cases, leaving the agent with incomplete context for effective use.

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, with the 'assetId' parameter clearly documented. The description does not add any additional meaning beyond the schema, such as examples of asset IDs or context about what information is retrieved. Baseline 3 is appropriate as the schema handles the parameter documentation adequately.

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 information') and resource ('an Algorand Standard Asset'), making the purpose evident. However, it does not differentiate from sibling tools like 'get_account_info' or 'get_transaction', which also retrieve information about different resources, leaving some ambiguity in scope.

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, such as 'get_account_info' for account details or 'get_transaction' for transaction data. There is no mention of prerequisites, exclusions, or specific contexts for its application.

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/Jake-loranger/algorand-mcp-server'

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