Skip to main content
Glama
devkindhq

machship-mcp

by devkindhq

Create Consignment with Existing Saved Items

machship_create_consignment_existing_items

Create a shipment consignment by referencing your company's saved items using their IDs or SKUs.

Instructions

Creates a consignment using previously saved company items (by item ID / SKU).

Args:

  • consignment (object): Consignment data referencing existing saved item IDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
consignmentYesConsignment data referencing existing item IDs
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the agent knows it's a mutation. The description adds 'creates' which is consistent, but does not provide additional behavioral context such as permissions, side effects, or the structure of the consignment object.

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 extremely concise, consisting of two sentences and an Args line. It delivers the core information without any extraneous text.

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

Completeness2/5

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

Despite annotations and schema coverage, the description lacks details about the consignment object's required fields, format of item IDs, or any constraints. A creation tool with a nested object parameter needs more guidance for correct invocation.

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% for the single parameter, which has a generic description. The tool description adds context about 'previously saved company items' but does not elaborate on the structure or required fields of the consignment object, so it adds limited extra meaning.

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 it 'creates a consignment using previously saved company items (by item ID / SKU)', which is a specific verb and resource, and distinguishes it from siblings like machship_create_consignment (general) and machship_create_consignment_with_complex_items (for complex 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 indicates it is for using existing saved items, which implies when not to use (if no existing items), but it does not explicitly name alternatives or exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/devkindhq/machship-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server