Skip to main content
Glama

w3_space_create

Create a new storage space with a custom name using the mcp-ipfs server. Run this command manually in your terminal to interactively generate recovery keys.

Instructions

Creates a new space with a user-friendly name. NOTE: w3 space create cannot be run via MCP due to interactive recovery key prompts. Please run this command manually in your terminal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoAn optional user-friendly name for the new space.

Implementation Reference

  • The handler function for 'w3_space_create', implemented as a stub that throws an error explaining the tool cannot be run via MCP because it requires interactive user input for recovery key prompts.
    const handleW3SpaceCreate: ToolHandler = async (_args) => {
      throw new Error(
        "`w3 space create` cannot be run via MCP due to interactive recovery key prompts. Please run this command manually in your terminal."
      );
    };
  • Zod schema defining the input arguments for the 'w3_space_create' tool, including an optional 'name' string parameter.
    export const W3SpaceCreateArgsSchema = z
      .object({
        name: z
          .string()
          .optional()
          .describe("An optional user-friendly name for the new space."),
      })
      .describe("Creates a new space with a user-friendly name.");
  • Export of the toolHandlers object that registers 'w3_space_create' mapped to its handler function, imported and used for dispatching in index.ts.
    // Tool Handlers Map
    export const toolHandlers: Record<string, ToolHandler> = {
      w3_login: handleW3Login,
      w3_space_ls: handleW3SpaceLs,
      w3_space_use: handleW3SpaceUse,
      w3_space_create: handleW3SpaceCreate,
      w3_up: handleW3Up,
      w3_ls: handleW3Ls,
      w3_rm: handleW3Rm,
      w3_open: handleW3Open,
      w3_space_info: handleW3SpaceInfo,
      w3_space_add: handleW3SpaceAdd,
      w3_delegation_create: handleW3DelegationCreate,
      w3_delegation_ls: handleW3DelegationLs,
      w3_delegation_revoke: handleW3DelegationRevoke,
      w3_proof_add: handleW3ProofAdd,
      w3_proof_ls: handleW3ProofLs,
      w3_key_create: handleW3KeyCreate,
      w3_bridge_generate_tokens: handleW3BridgeGenerateTokens,
      w3_can_blob_add: handleW3CanBlobAdd,
      w3_can_blob_ls: handleW3CanBlobLs,
      w3_can_blob_rm: handleW3CanBlobRm,
      w3_can_index_add: handleW3CanIndexAdd,
      w3_can_upload_add: handleW3CanUploadAdd,
      w3_can_upload_ls: handleW3CanUploadLs,
      w3_can_upload_rm: handleW3CanUploadRm,
      w3_plan_get: handleW3PlanGet,
      w3_account_ls: handleW3AccountLs,
      w3_space_provision: handleW3SpaceProvision,
      w3_coupon_create: handleW3CouponCreate,
      w3_usage_report: handleW3UsageReport,
      w3_can_access_claim: handleW3CanAccessClaim,
      w3_can_store_add: handleW3CanStoreAdd,
      w3_can_store_ls: handleW3CanStoreLs,
      w3_can_store_rm: handleW3CanStoreRm,
      w3_can_filecoin_info: handleW3CanFilecoinInfo,
      w3_reset: handleW3Reset,
    };
  • src/index.ts:94-125 (registration)
    MCP CallTool request handler that dispatches to the specific tool handler based on the tool name, using the imported toolHandlers map.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
      logger.info(`Handling CallTool request for: ${name}`);
    
      const handler = toolHandlers[name];
    
      if (!handler) {
        logger.error(`Unknown tool requested: ${name}`);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({ error: `Unknown tool: ${name}` }),
            },
          ],
          isError: true,
        };
      }
    
      try {
        const result = await handler(args);
        return result;
      } catch (error: any) {
        logger.error(`Error handling tool '${name}':`, error);
        return {
          content: [
            { type: "text", text: JSON.stringify({ error: error.message }) },
          ],
          isError: true,
        };
      }
    });
  • Special description override in the dynamic ListTools response, warning users that this tool cannot be used via MCP and must be run manually.
    if (toolName === "w3_space_create") {
      description +=
        " NOTE: `w3 space create` cannot be run via MCP due to interactive recovery key prompts. Please run this command manually in your terminal.";
    }
Behavior4/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 reveals a critical behavioral trait: the tool cannot be executed via MCP due to interactive prompts, requiring manual terminal use. This goes beyond the basic 'creates' action, disclosing execution constraints that are essential for the agent to know. However, it doesn't mention other potential behaviors like permissions needed, rate limits, or what happens on success/failure.

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 perfectly concise and well-structured: two sentences that each earn their place. The first sentence states the core purpose, and the second provides critical usage guidance with a clear NOTE prefix. There is zero wasted text, and the most important information (the limitation) is front-loaded in the second sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 creation operation with interactive prompts), no annotations, and no output schema, the description does a good job of covering the essential context. It explains the purpose and, crucially, the execution constraint that prevents MCP use. However, it doesn't describe what happens after creation (e.g., space ID returned, error conditions), which would be helpful given the lack of output schema.

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?

Schema description coverage is 100%, with the schema already documenting the single optional 'name' parameter. The description repeats 'with a user-friendly name' but adds no additional semantic context beyond what the schema provides (e.g., naming conventions, length limits, or examples). The baseline score of 3 is appropriate when 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 tool's purpose: 'Creates a new space with a user-friendly name.' It specifies the verb ('creates') and resource ('new space'), though it doesn't explicitly differentiate from sibling tools like 'w3_space_add' or 'w3_space_provision'. The purpose is clear but lacks sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance: 'NOTE: `w3 space create` cannot be run via MCP due to interactive recovery key prompts. Please run this command manually in your terminal.' This clearly states when NOT to use this tool (via MCP) and provides an alternative (manual terminal execution), which is crucial for avoiding failed invocations.

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