Skip to main content
Glama
Sign In
Deftship MCP Server

Deftship MCP Server

by Kodeas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Remove items from a batch

deftship_remove_batch_items

Remove specific items from a batch by item hash IDs, up to 10,000 items, and delete their associated shipment orders. Requires batch not in validating, processing, or completed status.

Instructions

Remove specific items from a batch by their item hash ids (max 10,000). Also deletes the associated shipment orders. The batch must not be validating, processing or completed.

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": {
      "batch_id": "<batch_id>",
      "batch_shipment_ids": "<batch_shipment_ids>"
    },
    "name": "deftship_remove_batch_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
batch_idYesThe batch hash id.
batch_shipment_idsYesItem hash ids to remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior1/5

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

The description states that the tool 'deletes the associated shipment orders,' which is a destructive side effect, but the annotations set destructiveHint=false. This contradiction undermines behavioral transparency. Additionally, no details about authorization, rate limits, or idempotency are provided.

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 concise with two sentences that contain all necessary information without extraneous words. It front-loads the primary action and includes the side effect and precondition efficiently.

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?

Given the simple operation and that schema covers all parameters, the description is mostly complete but lacks detail on error handling, transactional guarantees, and idempotency. The contradiction with annotations further reduces completeness.

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?

The input schema already has 100% description coverage for both parameters. The description adds further meaning by explaining that 'batch_shipment_ids' are item hash IDs and specifying the maximum count (10,000), which is not in the schema.

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 clearly states the tool removes specific items from a batch by item hash IDs, with a maximum of 10,000 items. It also notes the side effect of deleting associated shipment orders, which distinguishes it from sibling tools like 'deftship_add_batch_items'.

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?

The description provides clear context for when to use the tool (remove items from a batch) and includes a precondition (batch must not be in validating, processing, or completed state). However, it does not explicitly state when not to use it or mention alternatives like 'deftship_add_batch_items'.

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

Deploy Server

Other Tools