Skip to main content
Glama

w3_space_provision

Associates a decentralized storage space with a customer or billing account by linking a space DID to a customer identifier for simplified storage management.

Instructions

Associates a space with a customer/billing account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesCustomer identifier (e.g., email or account DID) to associate the space with.
spaceDidYesThe DID of the space to provision.

Implementation Reference

  • The handler function that implements the core logic for the w3_space_provision tool. It validates input using the schema, executes the w3cli 'space provision' command, and formats the response.
    const handleW3SpaceProvision: ToolHandler = async (args) => {
      const parsed = Schemas.W3SpaceProvisionArgsSchema.safeParse(args);
      if (!parsed.success)
        throw new Error(
          `Invalid arguments for w3_space_provision: ${parsed.error.message}`
        );
      const { customerId, spaceDid } = parsed.data;
      const { stdout } = await runW3Command(
        `space provision ${customerId} --space ${spaceDid}`
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              message: `Space ${spaceDid} provisioned for customer ${customerId}.`,
              output: stdout.trim(),
            }),
          },
        ],
      };
    };
  • Zod schema defining the input arguments for the w3_space_provision tool, including customerId and spaceDid.
    export const W3SpaceProvisionArgsSchema = z
      .object({
        customerId: z
          .string()
          .describe(
            "Customer identifier (e.g., email or account DID) to associate the space with."
          ),
        spaceDid: z
          .string()
          .startsWith("did:key:")
          .describe("The DID of the space to provision."),
      })
      .describe("Associates a space with a customer/billing account.");
  • The toolHandlers map registers the handleW3SpaceProvision function under the 'w3_space_provision' key, which is used by the MCP server to route CallTool requests.
    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,
    };
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 states the action ('associates') but doesn't clarify if this is a read-only or mutating operation, what permissions are required, potential side effects (e.g., billing implications), or error handling. This leaves significant gaps in understanding the tool's behavior beyond its basic purpose.

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 unnecessary words or redundancy. It is front-loaded with the core action, making it easy to parse and understand quickly, which is ideal for conciseness.

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?

Given the tool has 2 parameters with full schema coverage but no annotations and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavioral traits, usage context, or return values, which are important for a tool that likely involves billing or account management. This results in a moderate level of completeness with clear gaps.

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%, with clear descriptions for both parameters ('customerId' and 'spaceDid') in the input schema. The tool description adds no additional meaning beyond what the schema provides, such as format details or usage examples. However, since the schema fully documents the parameters, a baseline score of 3 is appropriate as the description doesn't compensate but also doesn't need to.

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 action ('associates') and the resources involved ('a space with a customer/billing account'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'w3_space_add' or 'w3_space_create', which might involve similar resources but different operations.

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, such as 'w3_space_add' or 'w3_space_create', nor does it mention prerequisites, exclusions, or specific contexts. It lacks explicit usage instructions, leaving the agent to infer based on the tool name and description 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

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