Skip to main content
Glama

w3_delegation_ls

List delegated storage permissions within the storacha.network using JSON-formatted output for clear and structured data retrieval in the MCP IPFS environment.

Instructions

Tool for w3_delegation_ls operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jsonNoFormat output as newline delimited JSON (default: true).

Implementation Reference

  • Main handler function for the w3_delegation_ls tool. Parses arguments using the schema, executes the 'delegation ls' command (with optional JSON flag), processes output using parseNdJson if JSON, and returns formatted content.
    const handleW3DelegationLs: ToolHandler = async (args) => {
      const parsed = Schemas.W3DelegationLsArgsSchema.safeParse(args);
      if (!parsed.success)
        throw new Error(
          `Invalid arguments for w3_delegation_ls: ${parsed.error.message}`
        );
      const { json } = parsed.data;
      const command = json ? "delegation ls --json" : "delegation ls";
      const { stdout } = await runW3Command(command);
      if (json) {
        const delegations = parseNdJson(stdout);
        return {
          content: [{ type: "text", text: JSON.stringify({ delegations }) }],
        };
      } else {
        return {
          content: [
            { type: "text", text: JSON.stringify({ output: stdout.trim() }) },
          ],
        };
      }
    };
  • Zod schema for input arguments of w3_delegation_ls, defining optional 'json' boolean flag defaulting to true.
    export const W3DelegationLsArgsSchema = z.object({
      json: z
        .boolean()
        .optional()
        .default(true)
        .describe("Format output as newline delimited JSON (default: true)."),
    });
  • Registration of the w3_delegation_ls handler in the toolHandlers map, which is likely exported and used for tool registration in the MCP system.
    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,
    };
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. It adds nothing beyond the tautological name restatement—no indication of whether this is a read/write operation, what permissions are needed, how results are returned, or any side effects. For a tool with zero annotation coverage, this is completely inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise ('Tool for w3_delegation_ls operation.') but this is under-specification rather than effective brevity. It wastes its single sentence on a tautology that provides no value, failing to front-load useful information. A more structured approach would clarify the tool's purpose upfront.

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

Completeness1/5

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

Given the tool's likely complexity (inferred from sibling tools involving delegations), no annotations, no output schema, and a minimal description, this is highly incomplete. The description doesn't explain what the tool returns, how to interpret results, or any operational context, leaving critical gaps for an agent to use it effectively.

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 1 parameter with 100% description coverage, documenting that 'json' controls output formatting. The description adds no parameter information beyond what the schema provides. With high schema coverage, the baseline is 3, as the schema handles the heavy lifting, but the description doesn't compensate or add any semantic context.

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

Purpose2/5

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

The description 'Tool for w3_delegation_ls operation' is a tautology that merely restates the tool name without explaining what the operation does. It doesn't specify what resource it acts on (delegations) or what 'ls' means (likely 'list'), nor does it differentiate from sibling tools like 'w3_delegation_create' or 'w3_delegation_revoke'. This provides minimal actionable information to an agent.

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

Usage Guidelines1/5

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

The description offers no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, and fails to reference related sibling tools (e.g., 'w3_delegation_create' for creating delegations or 'w3_ls' for broader listing). This leaves the agent with no usage direction.

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