Skip to main content
Glama
lnfi-network

RGB Lightning Network MCP Server

by lnfi-network

rgb_get_asset_metadata

Retrieve detailed metadata for a specific RGB asset by providing its unique asset ID, enabling access to essential asset information through the RGB Lightning Network MCP Server.

Instructions

Get metadata for a specific RGB asset

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetIdYesThe ID of the RGB asset

Implementation Reference

  • src/server.ts:104-119 (registration)
    Registration of the 'rgb_get_asset_metadata' MCP tool, including input schema, description, and inline handler function that delegates to RGBApiClientWrapper.getAssetMetadata
    server.tool(
      'rgb_get_asset_metadata',
      'Get metadata for a specific RGB asset',
      {
        assetId: z.string().describe('The ID of the RGB asset'),
      },
      async ({ assetId }) => {
        try {
          const metadata = await rgbClient.getAssetMetadata(assetId);
          return { content: [{ type: 'text', text: JSON.stringify(metadata, null, 2) }] };
        } catch (error) {
          const errorMessage = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: `Error: ${errorMessage}` }], isError: true };
        }
      }
    );
  • Inline handler function for the rgb_get_asset_metadata tool that fetches asset metadata via the RGB client and formats the response as MCP content
    async ({ assetId }) => {
      try {
        const metadata = await rgbClient.getAssetMetadata(assetId);
        return { content: [{ type: 'text', text: JSON.stringify(metadata, null, 2) }] };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return { content: [{ type: 'text', text: `Error: ${errorMessage}` }], isError: true };
      }
    }
  • Zod-based input schema defining the required 'assetId' parameter as a string
    {
      assetId: z.string().describe('The ID of the RGB asset'),
  • Helper method in RGBApiClientWrapper that wraps the underlying SDK call to retrieve RGB asset metadata, transforming assetId to asset_id
    async getAssetMetadata(assetId: string) {
      return await this.client.rgb.getAssetMetadata({ asset_id: assetId });
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's a 'Get' operation, implying read-only behavior, but doesn't mention any traits like permissions needed, rate limits, error conditions, or what the metadata includes (e.g., asset details, ownership info). This leaves significant gaps for a tool with no annotation coverage.

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 directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 complexity of asset metadata retrieval, no annotations, and no output schema, the description is incomplete. It doesn't explain what metadata is returned (e.g., asset properties, issuance details), potential errors, or how it differs from other asset-related tools, leaving the agent with insufficient 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 'assetId' clearly documented as 'The ID of the RGB asset'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline score of 3 where the schema does the heavy lifting.

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 'metadata for a specific RGB asset', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'rgb_get_asset_balance' or 'rgb_list_assets', which also retrieve asset-related information but with different scopes or data types.

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. It doesn't specify if this is for detailed metadata of a single asset, as opposed to listing assets or checking balances, leaving the agent to infer usage from the name alone without explicit context 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/lnfi-network/rgb-mcp-server'

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