Skip to main content
Glama
devkindhq

machship-mcp

by devkindhq

Group Consignments for Consolidation

machship_group_consignments_for_consolidation
Read-only

Groups consignments into consolidation groups based on options like carrier or route, providing a preview before final consolidation.

Instructions

Automatically groups consignments into consolidation groups based on options (carrier, route, etc.). Returns groups without actually consolidating — preview step before consolidation.

Args:

  • options (object): Consolidation grouping options (companyId, carrierId, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
optionsYesConsolidation grouping options
Behavior4/5

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

The description aligns with annotations (readOnlyHint=true) by stating it does not actually consolidate, and adds the preview step context. No behavioral traits beyond annotations are contradicted.

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 and a parameter line, front-loaded with the main action, and contains no fluff.

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?

Given the simple parameter and annotations, the description adequately explains purpose and behavior. Minor lack of return value details, but reasonable for a preview tool.

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 description adds examples of parameter keys (companyId, carrierId, etc.) beyond the schema's generic description, enhancing understanding of the 'options' object.

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 verb 'groups consignments' and the resource 'for consolidation', and distinguishes itself as a preview step before actual consolidation, differentiating it from tools that perform consolidation.

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 this tool is a preview step before consolidation, but does not explicitly mention when not to use it or name alternative tools for actual consolidation or other grouping purposes.

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