Pizza Developer

Delete work

delete_work

Destructive

Delete a work item. confirmName must equal the work's exact title.

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": {
      "id": "<id>",
      "confirmName": "<confirmName>"
    },
    "name": "delete_work"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Id of the Work.
`confirmName`	Yes	The Work's exact title, to confirm deletion.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026

addedInput schema / properties / confirmName

Added value: +{
+  "description": "The Work's exact title, to confirm deletion.",
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "id"
-]New value: +[
+  "id",
+  "confirmName"
+]

First observedOct 3, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered structurally. The description adds a genuinely useful behavioral guard (confirmName must match the exact title), but says nothing about irreversibility, cascade effects on associated work, or failure behavior.

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?

Two sentences, zero filler, action front-loaded before the confirmation constraint.

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?

A destructive, non-idempotent tool with no output schema needs a bit more about what deletion means permanently. The confirmation safeguard helps, but the absence of any mention of permanence or the archive alternative leaves a meaningful gap.

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%, and both parameters are documented there, so the schema carries the burden. The description restates the confirmName contract but adds no format, casing, or matching nuance beyond 'exact title'.

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?

States a specific verb and resource ('Delete a work item'), so the agent knows exactly what is affected. It does not differentiate itself from sibling deletion tools (delete_batch, delete_idea, delete_project) or from the non-destructive 'archive' alternative, but the resource is unambiguous.

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?

No guidance on when to delete versus the sibling 'archive' tool, which is the obvious softer alternative for a work item. The only usage instruction is the mechanical confirmation requirement, which is a precondition rather than a when-to-use rule.

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

All Pizza Developer 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?