Skip to main content
Glama
Sign In
clm-mcp

clm-mcp

by sabadia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

clm_shipment_command_update_shipment_comment

Idempotent

Update an existing shipment comment by specifying the item ID and the new comment text. Replace outdated or incorrect shipment remarks directly.

Instructions

Updates the text of an existing shipment comment.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already indicate the operation is idempotent and non-destructive. The description adds limited context by clarifying that only the text is updated, not the comment as a whole, but it does not explain behavior when the comment does not exist or whether a null Comment clears the text.

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?

A single, front-loaded sentence with no filler. Every word contributes to stating what the tool does.

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?

With 0% schema description coverage, the description must compensate by explaining how to provide the comment identifier and new text. It does not do so, nor does it cover usage guidance. The output schema and annotations help, but the description alone leaves an agent guessing about required inputs and failure behavior.

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 provides no descriptions for ItemId or Comment, so the description's mention of 'text' and 'existing shipment comment' adds some meaning. However, it does not explicitly map these concepts to the parameters or clarify which identifier is needed to locate the comment.

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 uses a specific verb ('Updates') and a precise resource ('the text of an existing shipment comment'). It clearly distinguishes this tool from the sibling create and delete comment tools by specifying 'existing' and 'text.'

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?

No guidance is provided about when to use this tool versus creating a new comment or deleting a comment. The word 'existing' implies it is not for creation, but no alternatives or exclusions are stated.

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