Skip to main content
Glama

w3_can_blob_ls

List and retrieve blobs stored in the current space with pagination support and JSON output format using the MCP IPFS server.

Instructions

Lists blobs stored in the current space.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoOpaque cursor string from a previous response for pagination.
jsonNoFormat output as newline delimited JSON (default: true).
sizeNoDesired number of results to return.

Implementation Reference

  • The handler function for 'w3_can_blob_ls' that validates input with schema, builds and runs the 'can blob ls' CLI command, processes output based on json flag, and returns structured response.
    const handleW3CanBlobLs: ToolHandler = async (args) => {
      const parsed = Schemas.W3CanBlobLsArgsSchema.safeParse(args);
      if (!parsed.success)
        throw new Error(
          `Invalid arguments for w3_can_blob_ls: ${parsed.error.message}`
        );
      const { json, size, cursor } = parsed.data;
      let command = "can blob ls";
      if (json) command += " --json";
      if (size) command += ` --size ${size}`;
      if (cursor) command += ` --cursor ${cursor}`;
      const { stdout } = await runW3Command(command);
      if (json) {
        const blobs = parseNdJson(stdout);
        return {
          content: [{ type: "text", text: JSON.stringify({ blobs }) }],
        };
      } else {
        return {
          content: [
            { type: "text", text: JSON.stringify({ output: stdout.trim() }) },
          ],
        };
      }
    };
  • Zod schema for input validation of 'w3_can_blob_ls' tool arguments: optional json (default true), size, cursor.
    export const W3CanBlobLsArgsSchema = z
      .object({
        json: z
          .boolean()
          .optional()
          .default(true)
          .describe("Format output as newline delimited JSON (default: true)."),
        size: z
          .number()
          .int()
          .positive()
          .optional()
          .describe("Desired number of results to return."),
        cursor: z
          .string()
          .optional()
          .describe(
            "Opaque cursor string from a previous response for pagination."
          ),
      })
      .describe("Lists blobs stored in the current space.");
  • Maps the tool name 'w3_can_blob_ls' to its handler function in the toolHandlers export.
    w3_can_blob_ls: handleW3CanBlobLs,
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 mentions listing blobs but doesn't describe key behaviors like pagination (implied by the 'cursor' parameter), output format details, or potential rate limits. This leaves significant gaps for a tool with 3 parameters and no output schema.

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 zero 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list operation with 3 parameters and no output schema, the description is minimal but functional. It covers the basic action but lacks details on output format, pagination behavior, or error conditions, which would be helpful given the complexity. The high schema coverage helps, but more context is needed for full completeness.

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 schema description coverage is 100%, so the schema already documents all parameters ('cursor', 'json', 'size') thoroughly. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline for high coverage but not providing extra value.

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 ('Lists') and resource ('blobs stored in the current space'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'w3_can_blob_add' (adds blobs) or 'w3_can_blob_rm' (removes blobs), which would require 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?

The description provides no guidance on when to use this tool versus alternatives like 'w3_can_store_ls' or 'w3_can_upload_ls', nor does it mention prerequisites such as needing to be in a specific space. It only states what it does, not when to use it.

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

Related 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/alexbakers/mcp-ipfs'

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