Cloudlabels

Delete stock movement

delete_stock_movement

Destructive

Requires items.delete. Delete a draft stock movement. Posted movements are refused with 409. Inventory is not reversed because a draft was never posted. Two-step confirm_token: the first call without confirm_token only returns confirmation_required, a summary, and confirm_token. That call does not write, delete, cancel, or send. The second call must repeat the same arguments plus that confirm_token; that is the write. A confirm boolean is ignored. The token expires in 5 minutes and works once.

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": {
      "movement_id": "<movement_id>"
    },
    "name": "delete_stock_movement"
  }
}

Input Schema

Name	Required	Description	Default
`movement_id`	Yes
`confirm_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: draft-only deletion, 409 refusal for posted movements, no inventory reversal, the two-step confirm_token flow, that the first call is non-writing, that a confirm boolean is ignored, and that the token expires in five minutes and is single-use. These details are consistent with the destructiveHint=true annotation.

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 dense but front-loaded: permission, draft constraint, refusal behavior, and confirmation mechanics appear in a logical order. Every sentence carries operational information relevant to invoking the tool correctly.

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

Completeness5/5

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

For a two-parameter mutation with no output schema, the description covers permissions, preconditions, failure behavior, side effects, and the confirm_token protocol. It gives the agent everything needed to call the tool correctly without needing return-value details.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It thoroughly explains confirm_token semantics, including the two-step flow, single use, and five-minute expiry, though movement_id is only implicitly described as the target of the delete operation.

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

Purpose5/5

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

The description uses the specific verb 'delete' with the resource 'draft stock movement' and immediately distinguishes valid targets from posted movements, which are refused. This is enough for an agent to understand the operation without opening another tool.

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

Usage Guidelines4/5

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

It clearly states when the tool applies: draft movements only, with posted movements refused via 409, and notes the required 'items.delete' permission. It does not explicitly name an alternative such as cancel_stock_movement for posted movements, so it stops short of full when/when-not/alternative guidance.

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

All Cloudlabels tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?