Skip to main content
Glama

Coline

Comment on an issue

comment_on_upstream_issue

Posts a comment on an Upstream issue 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_upstream_issue"
  }
}

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.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so safety and scope are covered structurally. The description adds that the comment is attributed to 'the person' (acting on the user's identity), which is genuine context beyond the annotations, but it does not warn that non-idempotent posting can create duplicate comments on retry.

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, front-loading the action and following with the usage gate; there is no filler. It is arguably too terse for a write tool, but nothing is wasted.

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?

An output schema exists, so return values need not be described, and annotations carry the safety profile. Still, for a four-parameter write operation with half the parameters undocumented, the definition says nothing about issue-number semantics, body limits, or what happens if the comment cannot be posted.

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 coverage is only 50%: 'workspace' and 'repository' are documented in the schema, but 'number' and 'body' carry no description anywhere. The description adds no meaning about what 'number' refers to (issue number) or what constrains 'body', so the undocumented half stays unexplained.

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?

The description gives a specific verb ('Posts a comment') and resource ('an Upstream issue'), which separates it from comment_on_change_request and comment_on_sheet by target type. It stops short of naming those siblings explicitly, so the differentiation is implicit rather than stated.

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 only when they clearly want it posted' is a real gating condition and useful for an agent deciding whether to act. However, it offers no alternatives (e.g., when to use update_upstream_issue or read the issue first) and 'clearly want it posted' is left to interpretation with no concrete signals.

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