Skip to main content
Glama
Sign In
Deftship MCP Server

Deftship MCP Server

by Kodeas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Void a parcel shipment

deftship_void_parcel
Destructive

Cancel a parcel order using its shipment order ID. Confirmation is required to proceed; a void fee may apply.

Instructions

Void a previously created parcel order by shipment_order_id. May incur a void fee (returned as void_fee). Requires confirm=true.

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": {
      "shipment_order_id": "<shipment_order_id>"
    },
    "name": "deftship_void_parcel"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be set to true to actually execute this action. This operation charges your Deftship balance or is otherwise irreversible. Confirm with the user before setting true.
shipment_order_idYesThe shipment order id to void.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds that a void_fee may be incurred, providing useful behavioral context beyond annotations.

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: first states purpose, second adds key constraints and fee. No extraneous words. Front-loaded effectively.

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?

Covers core action, identification, confirmation requirement, and fee. Lacks mention of irreversible nature (covered by schema and annotations) and behavior when confirm is false. Adequate for a simple tool with annotations.

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 has 100% coverage with detailed descriptions. The description adds the potential void_fee return and reiterates the confirm=true requirement, though the schema already explains confirm's role.

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?

Clearly states the action 'Void a previously created parcel order' and the identifier 'shipment_order_id'. Distinguishes from sibling tools that void other types (freight, insurance, pickup).

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?

Specifies the confirm=true requirement, guiding safe usage. Does not explicitly exclude alternatives or state when not to use, but the sibling names imply this is for parcel orders only.

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