Skip to main content
Glama

resolve_issue

Mark a review issue's status as RESOLVED. IMPORTANT RESTRICTION: Do NOT call this tool automatically after fixing an issue. Only the human user is allowed to approve and resolve issues (or explicitly instruct you to call resolve_issue). Instead, post your fix summary using add_issue_comment and recommend that the user resolve the issue.

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": {
      "issueSlugId": "<issueSlugId>"
    },
    "name": "resolve_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueSlugIdYesUnique slug ID of the issue to mark as RESOLVED (e.g. 'ISS-xxxxxx').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / issueSlugId / description
      Previous value: -"The slug ID of the Issue (e.g. 'ISS-xxxxxx')"New value: +"Unique slug ID of the issue to mark as RESOLVED (e.g. 'ISS-xxxxxx')."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose the most important behavioral trait: this is a human-gated mutation that must not be auto-invoked. It does not describe the response, error behavior, or whether a resolved issue can be reopened, leaving a minor gap for a mutation tool.

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?

Short and front-loaded: the action comes first, then the restriction, then the recommended alternative. The capitalized IMPORTANT marker earns its space, though the parenthetical restating of the tool name is slightly redundant.

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 one-parameter mutation with no output schema, the description covers the critical policy gate and the fallback workflow. It omits what a successful resolution returns or whether the issue must currently be open, but these are secondary given the tool's simplicity.

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% and the single issueSlugId parameter is fully documented in the schema (including the 'ISS-xxxxxx' format). The description adds no further meaning about the parameter, so the 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?

States a specific verb and resource ("Mark a review issue's status as RESOLVED") and explicitly names the sibling tool to use instead (add_issue_comment), so the agent can distinguish it from other issue-related siblings without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-not-to-use rule ("Do NOT call this tool automatically after fixing an issue"), the condition required to use it (human approval or explicit instruction), and the concrete alternative workflow (post a summary via add_issue_comment and recommend the user resolve).

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