Skip to main content
Glama
Sign In
clm-mcp

clm-mcp

by sabadia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

clm_smart_shipment_command_save_smart_shipment_wizard_materials

Idempotent

Save delivery materials and drop-off details (building, floor, laydown area, recipient team) for Smart Shipment wizard step 4, persisting lines for new drafts or storing on the existing shipment's smart-draft.

Instructions

Saves step 4 of the Smart Shipment wizard: the delivery materials and drop-off details (building, floor, laydown area, recipient team) for the shipment. For a new (drafted) shipment this persists the material lines to the shipment and saves each ShipmentMaterial individually; for an existing shipment it stores the material info on the shipment's smart-draft instead.

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": {
      "params": "<params>"
    },
    "name": "clm_smart_shipment_command_save_smart_shipment_wizard_materials"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only state idempotent and non-destructive, leaving the description to explain what happens during the save. It does that well: for new shipments it persists material lines and saves each ShipmentMaterial individually, while for existing shipments it stores on the smart-draft instead. This discloses meaningful behavioral nuance beyond the 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?

The description is two tight sentences with no filler. It front-loads the core purpose, then adds the condition-dependent behavior in the second sentence. Every part earns its place.

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 an output schema exists and annotations cover safety/idempotency, the description covers the essential behavioral split between new and existing shipments. It could be slightly more complete by explicitly routing to sibling wizard-step tools or explaining what a 'smart-draft' is, but nothing critical is missing for invoking the tool.

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?

The schema has 0% description coverage, so the description must carry the parameter-semantics burden. It maps several key concepts to parameters: 'building, floor, laydown area, recipient team' and 'delivery materials'. However, it does not clarify ShipmentId, BookingDate, CommissionedId, MaterialComment, or the distinction/relationship between RecipientTeamId and RecipientTeamName, and the Materials array item shape is left vague.

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 names a specific verb ('Saves'), a specific resource ('step 4 of the Smart Shipment wizard'), and the exact content ('delivery materials and drop-off details'). It clearly distinguishes this tool from sibling wizard-step savers by identifying the step and the data involved.

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 gives clear context: it is for the Smart Shipment wizard, step 4, and differentiates behavior between new drafts and existing shipments. It does not explicitly name alternative tools or state when not to use it, but the sibling list makes the intended placement fairly inferable.

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