Skip to main content
Glama
lnfi-network

RGB Lightning Network MCP Server

by lnfi-network

rgb_list_assets

Retrieve a complete list of all RGB assets currently available in your RGB Lightning node for asset management and tracking purposes.

Instructions

List all RGB assets available in the node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function for 'rgb_list_assets' that invokes rgbClient.listAssets with empty filter and returns the JSON-formatted result or error response.
    async ({}) => {
      try {
        // Pass the correct filter object structure expected by the API
        const assets = await rgbClient.listAssets({ filter_asset_schemas: [] });
        return { content: [{ type: 'text', text: JSON.stringify(assets, null, 2) }] };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return { content: [{ type: 'text', text: `Error: ${errorMessage}` }], isError: true };
      }
    }
  • src/server.ts:51-65 (registration)
    Registers the 'rgb_list_assets' MCP tool with empty input schema and inline handler.
    server.tool(
      'rgb_list_assets',
      'List all RGB assets available in the node',
      {},
      async ({}) => {
        try {
          // Pass the correct filter object structure expected by the API
          const assets = await rgbClient.listAssets({ filter_asset_schemas: [] });
          return { content: [{ type: 'text', text: JSON.stringify(assets, null, 2) }] };
        } catch (error) {
          const errorMessage = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: `Error: ${errorMessage}` }], isError: true };
        }
      }
    );
  • Helper method in RGBApiClientWrapper that wraps the SDK's listAssets call, ensuring the filter object has 'filter_asset_schemas' field.
    async listAssets(filter?: any) {
      // The API expects an object with filter_asset_schemas field
      // If filter is provided and is a proper object with filter_asset_schemas, use it
      // Otherwise, default to empty filter
      if (filter && typeof filter === 'object' && 'filter_asset_schemas' in filter) {
        return await this.client.rgb.listAssets(filter);
      } else {
        return await this.client.rgb.listAssets({ filter_asset_schemas: [] });
      }
    }
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. It states it 'List all RGB assets' but doesn't disclose behavioral traits like whether it returns a paginated list, requires authentication, has rate limits, or what format the output takes. This is a significant gap 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 with no wasted words. It is 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 tool's complexity (a list operation with no parameters) and lack of annotations and output schema, the description is incomplete. It doesn't explain what 'all RGB assets' entails (e.g., format, scope, or limitations), leaving gaps in understanding for the agent.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, earning a baseline 4 as it appropriately omits unnecessary details.

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 ('List') and resource ('RGB assets available in the node'), making the purpose specific and understandable. It doesn't explicitly distinguish from siblings like 'rgb_get_asset_balance' or 'rgb_get_asset_metadata', which could provide more targeted asset information, so it doesn't reach 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 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. For example, it doesn't mention if this is for a broad overview versus using 'rgb_get_asset_balance' for specific asset details, leaving the agent without usage context.

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