Skip to main content
Glama
Pirate Ship MCP Server

Pirate Ship MCP Server

Delete saved package

delete_saved_package
Destructive

Permanently removes a saved package (box size and weight preset) from your account. Use it to clear presets you no longer ship with; existing labels remain unaffected.

Instructions

Delete a Saved Package (box size and weight preset) from the account.

Removes it for good; labels already made with it are not affected. To change its size or weight instead, use update_saved_package. Returns the deleted package's id.

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": {
      "package_id": "<package_id>"
    },
    "name": "delete_saved_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
package_idYesid from list_saved_packages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Adds real context beyond the annotations: permanence ('removes it for good') and the key blast-radius fact that existing labels are unaffected. It also notes the return value. Minor gaps remain around behavior when the package_id does not exist or is referenced by active workflows.

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

Conciseness4/5

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

Three short sentences, front-loaded with the operation, then side effects, then alternatives, then return value. No filler; each sentence conveys a distinct fact.

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

Completeness4/5

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

For a one-parameter destructive operation with annotations covering the safety profile and no output schema, this covers outcome, side effects, alternative, and return value. Only failure modes (missing id, in-use preset) are absent.

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?

Single parameter with 100% schema description coverage ('id from list_saved_packages'), so the schema already carries the meaning. The description adds no parameter detail, which is acceptable at this coverage level but not value-adding.

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?

States a specific verb and resource ('Delete a Saved Package') and immediately defines the entity as a 'box size and weight preset', which an agent cannot infer from the name alone. It is clearly separable from list_saved_packages, create_saved_package and update_saved_package.

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?

Explicitly routes modification intent to update_saved_package, which is the main ambiguity for this tool. It does not state what to do if the preset is unknown or in use, so the when-not guidance is partial rather than complete.

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