Skip to main content
Glama
Sign In
clm-mcp

clm-mcp

by sabadia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

clm_get_incident

Read-onlyIdempotent

Retrieve full details for any incident or finding by providing its item ID, enabling quick investigation and resolution.

Instructions

Retrieve the full detail of a single incident/finding.

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": {
      "item_id": "<item_id>"
    },
    "name": "clm_get_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesThe incident's item id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description's 'Retrieve' is consistent with those. The description adds no additional behavioral context such as data scope, auth, or side effects, but none are needed given 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?

A single sentence communicates the operation, resource, and cardinality with no filler or redundancy. It is appropriately front-loaded and easy to scan.

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

Completeness5/5

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

For a simple read-only lookup with one fully documented required parameter, an output schema, and read-only/idempotent annotations, the description is complete enough for an agent to select and 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?

Schema coverage is 100%: item_id is described as 'The incident's item id.' The description adds no further parameter-level meaning, so the schema-supported baseline of 3 applies.

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 ('Retrieve'), a specific resource ('incident/finding'), and a scope ('single', 'full detail'), which clearly distinguishes it from sibling tools like clm_list_incidents and the incident command tools.

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 singular scope implies this is for retrieving one incident by ID, but it never explicitly states when to choose this over clm_list_incidents or other incident-related siblings. No exclusions or alternative routing are provided.

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