Skip to main content
Glama
Sign In
Deftship MCP Server

Deftship MCP Server

by Kodeas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Void a pickup

deftship_void_pickup
Destructive

Void a pickup order by its ID. Requires confirm=true to execute the irreversible action.

Instructions

Void a previously created pickup order by id. 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": {
      "pickup_order_id": "<pickup_order_id>"
    },
    "name": "deftship_void_pickup"
  }
}

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.
pickup_order_idYesThe pickup order id to void.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true, but the description adds valuable behavioral context by noting that the operation is irreversible and charges the user's balance. This goes beyond the annotation signal.

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 concise sentences that front-load the core action and then state the critical requirement. Every word is purposeful with no filler.

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 tool with full schema coverage and no output schema, the description covers the essential purpose and constraint. However, it omits information about the return value or post-void state, which could help an agent understand the complete impact.

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 coverage is 100%, and the description reiterates the confirm requirement, but adds no new meaning beyond what the schema provides for the pickup_order_id parameter. Baseline score of 3 is appropriate.

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 action (void) and the resource (previously created pickup order by id). It is specific and distinguishes the tool from sibling void tools that target different resources (freight, insurance, parcel).

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?

The description specifies the confirm=true requirement but fails to provide guidance on when to use this tool versus its siblings (e.g., deftship_void_freight, deftship_void_parcel). No explicit context or exclusion criteria are given.

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