Skip to main content
Glama

project_optimize

DestructiveIdempotent

Queue storage sharing for verified snapshots on clone-capable volumes while preserving paths, content, permissions, timestamps, and external files; skip unsupported files and report paths/free space.

Instructions

Queue storage sharing with existing verified snapshots on clone-capable volumes. Every project path, byte content, permission, modification time and attempt remains; original external files and archives stay in place. Files without snapshots or cloning support are skipped. Release the task lease before polling operation_get; the receipt records each path and observed free space.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>",
      "revision": "<revision>",
      "op_id": "<op_id>"
    },
    "name": "project_optimize"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
tokenNo
task_idYes
revisionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, and non-open-world. The description adds the preservation guarantee, skip rule, task-lease release before operation_get, and receipt contents, which are meaningful beyond the annotations; it still does not clarify exactly what destructive change occurs or how to acquire the lease.

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?

Four compact sentences, front-loaded with purpose and followed by preservation, skip behavior, and the polling workflow. No filler; density is justified for a destructive asynchronous operation.

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?

The description covers core behavior and post-call workflow, and an output schema exists for receipts. However, for a destructive operation with four undocumented parameters it leaves the mechanism and parameter roles unclear, so an agent still lacks enough to invoke it reliably without schema inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description does not define task_id, revision, op_id, or token. 'task lease' and operation_get imply a workflow mapping but do not explain which parameter is the lease, what revision means, or how op_id is obtained.

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 first sentence gives a specific action: queueing storage sharing for a project using existing verified snapshots on clone-capable volumes. It distinguishes this from snapshot creation by requiring existing snapshots, though 'storage sharing' is jargon and the project-optimization outcome is only implied.

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

Usage Guidelines3/5

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

It supplies preconditions (verified snapshots, clone-capable volumes) and skip behavior, plus a post-call polling instruction. It does not explicitly say when to choose this over alternatives such as project_snapshot or project_export, nor when not to use it beyond file-level skips.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.