Skip to main content
Glama
Sign In
clm-mcp

clm-mcp

by sabadia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

clm_material_handover_command_change_material_handover_status

Destructive

Change a material handover status between InProgress and Paused, adding a handover event with note and photos, and updating the parent shipment's status. Pausing also queues thumbnail generation for responsible-person photos.

Instructions

Toggles a handover's status between InProgress and Paused, appending a new handover event capturing the note and photos for the change, and updates the parent shipment's aggregated handover status. Pausing also queues a background job to generate thumbnails for the responsible-person photos of that event.

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_material_handover_command_change_material_handover_status"
  }
}

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
Behavior5/5

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

Discloses multiple side effects beyond the destructiveHint annotation: appends a new handover event with note and photos, updates the parent shipment's aggregated handover status, and queues a background thumbnail-generation job on pause. This gives an agent a clear model of what invoking the tool will change.

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, front-loaded with the primary state transition, then side effects in logical order. Every sentence earns its place and there is no filler.

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 the core action, side effects, and key parameters, and an output schema exists so return-value details are not needed. The only notable gap is the undocumented ItemId and somewhat implicit Status semantics, but an agent still has enough context to invoke the tool correctly.

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 no per-property descriptions (0% coverage), and the description only partially compensates. It explains Note, MaterialPhotos, and ResponsiblePersonPhotos via 'note and photos' and the thumbnail job, and clarifies InProgress/Paused as Status values. However, ItemId is never explicitly explained, and there is no guidance on required vs optional fields.

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?

Description opens with 'Toggles a handover's status between InProgress and Paused,' naming the exact verb, resource, and allowed transitions. This clearly differentiates it from sibling tools like complete_material_handover and create_material_handover.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The toggling language implies use for pausing or resuming a handover, but there is no explicit when-to-use/when-not-to-use guidance and no reference to alternative sibling tools. The existence of complete_material_handover makes this guidance more valuable, but it is only implied.

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