Skip to main content
Glama
Sign In
clm-mcp

clm-mcp

by sabadia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

clm_incident_command_create_incident

Create an incident for a CLM, KonsHub, or equipment-booking shipment, link it to the shipment, and update incident counts. Background tasks generate thumbnails and regenerate PDFs for completed shipments.

Instructions

Creates a new incident/finding against a CLM, KonsHub, or equipment-booking shipment, links it to the shipment, and recalculates the shipment's incident counts. A background command is queued afterwards to generate thumbnails for the incident's attached files, and, if the shipment is already completed, to trigger PDF regeneration.

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

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?

Annotations only say destructiveHint=false, so the description carries the burden of side-effect disclosure. It explicitly discloses that the incident is linked, shipment counts are recalculated, a background command queues thumbnail generation, and PDF regeneration may be triggered for completed shipments—valuable behavioral detail beyond the annotation.

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 with no filler: the primary action is front-loaded, followed by the side effects and conditional background behavior. Every clause adds information needed for safe invocation.

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

Completeness3/5

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

The description is strong on behavioral context and return values are covered by the output schema, but the tool has six nested fields with zero schema descriptions and incomplete parameter guidance. It is not complete enough for an agent to reliably fill all parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it only loosely maps to Files and ShipmentId. Type, ItemId, Remark, and IncidentType are never defined, leaving an agent unable to construct the params object correctly with confidence.

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 opens with a specific action and resource: 'Creates a new incident/finding against a CLM, KonsHub, or equipment-booking shipment.' It also states the linking and count-recalculation behavior, and the verb 'creates' clearly separates it from sibling update/delete/get incident tools.

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 provides clear context—an agent should use this when an incident/finding needs to be created and attached to a shipment. It does not mention explicit when-not-to-use cases or named alternatives, but the creation semantics make the intended use unambiguous.

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