Skip to main content
Glama

Comment on an incident

comment_on_incident

Adds a comment to the incident's timeline, seen only by the workspace (Pro plans). Use it to record what you found or did. Free.

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": {
      "incident_id": "<incident_id>",
      "message": "<message>"
    },
    "name": "comment_on_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe comment's text.
incident_idYesIncident ID from list_incidents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / message / description
      Added value: +"The comment's text."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description adds genuinely useful behavior beyond the annotations: the comment lands on the incident timeline and is visible only to the workspace, plus a plan prerequisite. It does not address duplication (annotations declare idempotentHint=false, so repeated calls create repeat comments) or any ordering/locking behavior on the timeline, and the trailing 'Free.' conflicts confusingly with the '(Pro plans)' qualifier.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences carry the core meaning efficiently. The dangling one-word 'Free.' adds no actionable information and muddies the plan gate already stated as '(Pro plans)', costing some structure points.

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?

For a simple two-parameter write tool with full schema coverage, no output schema, and annotations covering the safety profile, the description supplies what is needed: what gets created, where it appears, and who can see it. Only the contradictory plan wording and the unaddressed non-idempotent behavior keep it from full marks.

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 description coverage is 100%, with both incident_id and message documented in the schema, so the baseline is 3. The description adds only the idea that the message is a record of findings; it does not clarify format, mention the 2000-character cap, or explain how incident_id relates to list_incidents output beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Adds a comment to the incident's timeline') and adds a visibility scope ('seen only by the workspace'), so the agent knows exactly what is created. It does not name the closest sibling, post_incident_update, so the boundary between a private comment and a public incident update is left implicit.

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?

'Use it to record what you found or did' gives a usage context but no when-not guidance and no named alternative. The agent must infer on its own whether a status change belongs here or in post_incident_update or update_incident.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources