Skip to main content
Glama

list_blobs

Retrieve a list of stored data objects from the Walrus decentralized storage network, with optional limit control for managing results.

Instructions

List stored blobs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of blobs to list (default: 10)

Implementation Reference

  • MCP tool handler for list_blobs: parses arguments using schema, calls walrusClient.listBlobs(), and returns JSON-formatted result as text content.
    case 'list_blobs': {
      const { limit = 10 } = ListBlobsSchema.parse(args);
      const result = await walrusClient.listBlobs(limit);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Zod input schema for list_blobs tool, defining optional 'limit' parameter.
    const ListBlobsSchema = z.object({
      limit: z.number().optional().describe('Maximum number of blobs to list (default: 10)'),
    });
  • src/index.ts:88-101 (registration)
    Tool registration in ListToolsResponse: defines name, description, and inputSchema for list_blobs.
    {
      name: 'list_blobs',
      description: 'List stored blobs',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Maximum number of blobs to list (default: 10)',
            default: 10,
          },
        },
      },
    },
  • WalrusClient helper method implementing listBlobs logic, which warns about missing native API and returns empty array.
    async listBlobs(limit: number = 10): Promise<string[]> {
      // Note: Walrus doesn't provide a native list blobs API
      // This would typically require maintaining a local index or using Sui blockchain queries
      // For now, return empty array with a note
      console.warn('listBlobs: Walrus does not provide native blob listing. Consider maintaining a local index.');
      return [];
    }
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 'List stored blobs' but does not reveal key traits: whether it's read-only (implied but not explicit), how results are ordered or paginated, if authentication is required, or potential rate limits. For a list operation with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 extremely concise at three words, with zero wasted text. It is front-loaded and directly states the tool's action without unnecessary elaboration, making it efficient for quick comprehension.

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 incomplete for a list tool. It does not explain return values (e.g., blob names, metadata, or pagination tokens), error conditions, or dependencies. While the schema covers the single parameter well, the overall context for effective tool use is insufficient.

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 'limit' parameter fully documented. The description does not add any meaning beyond the schema, as it mentions no parameters. According to the rules, when schema coverage is high (>80%), the baseline score is 3 even without parameter info in the description, which applies here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List stored blobs' clearly states the verb ('List') and resource ('stored blobs'), making the purpose understandable. However, it lacks specificity about scope (e.g., all blobs vs. filtered) and does not distinguish it from sibling tools like 'get_blob' or 'get_blob_info', which might retrieve individual blobs or metadata. This vagueness prevents a higher 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. It does not mention sibling tools like 'get_blob' (for retrieving a specific blob) or 'get_blob_info' (for metadata), nor does it specify contexts such as browsing vs. targeted access. Without any usage instructions, the agent must infer from tool names alone.

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/Motion-Labs-Sui/walrus-mcp'

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