Skip to main content
Glama

Coline

Comment on a change request

comment_on_change_request

Posts a comment on a change request's conversation as the person. Use it only when they clearly want it posted.

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": {
      "workspace": "<workspace>",
      "repository": "<repository>",
      "number": "<number>",
      "body": "<body>"
    },
    "name": "comment_on_change_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
numberYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
repositoryYesRepository name in this workspace, from list_repositories.

Output Schema

NameRequiredDescriptionDefault
urlYes
commentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent write, so the safety profile is covered. The description adds real value with 'as the person' (visible attribution) and the explicit confirmation guardrail, but says nothing about duplicate comments, permissions, or failure modes.

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 sentences with the action front-loaded and the guardrail second. The phrase 'clearly want it posted' is slightly vague about what 'it' refers to, costing a point.

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?

This is a mutation tool with an output schema and partial parameter documentation, so the burden is moderate. The description covers attribution and consent but leaves duplicate-posting behavior and permission requirements unaddressed.

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 50% – workspace and repository are documented in the schema, while number and body are not. The description implicitly clarifies that number targets a change request and body is the comment text, which is modest compensation but does not cover the 20,000-character body limit or other constraints.

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: posts a comment on a change request's conversation, and clarifies it is attributed to the person. The 'change request' resource differentiates it from comment_on_sheet and comment_on_upstream_issue without needing to name them.

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?

Provides one usage constraint – post only when the person clearly wants it – which is a useful consent gate but not a routing rule. It does not say when to prefer a different tool or what to do if the target change request is ambiguous.

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