Skip to main content
Glama

Close GitHub Issue with Resolution Entry

close_github_issue_with_entry

Closes a GitHub issue and records a journal entry documenting its resolution, keeping project history tied to the closed issue.

Instructions

Close a GitHub issue AND create a journal entry documenting the resolution.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "close_github_issue_with_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoRepository name - LEAVE EMPTY to auto-detect
tagsNoJournal entry tags
ownerNoRepository owner - LEAVE EMPTY to auto-detect
commentNoComment to add to the issue before closing
use_test_dbNo
issue_numberNoIssue number to close
move_to_doneNoMove the associated Kanban item to "Done" column
project_numberNoGitHub Project number (required if move_to_done is true, or uses DEFAULT_PROJECT_NUMBER)
resolution_notesNoNotes about how the issue was resolved

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
issueNo
kanbanNo
detailsNoAdditional error context
messageNo
successNo
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
instructionNo
recoverableNoWhether the error is recoverable
journalEntryNo
aggregated_errorsNoDetails of individual errors in a multi-step operation
requiresUserInputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv9.1.0
    • changedInput schema / properties / issue_number / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
    • changedInput schema / properties / project_number / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv9.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and non-idempotency, so the mutation and external-call profile is covered. The description adds the useful fact that a second artifact (a journal entry) is produced, but says nothing about the implicit Kanban move, whether the comment is posted before or after closing, or what happens if the journal write fails after the issue closes.

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?

One front-loaded sentence with zero filler, and the capitalized AND correctly signals that two side effects occur. It is on the thin side for a nine-parameter composite tool, but nothing is redundant.

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?

With an output schema present and high schema coverage, the description does not need to explain return values. However, for a tool that performs three distinct mutations (comment, close, journal entry, plus an optional Kanban move), the absence of any note about atomicity or the optional board update leaves a meaningful gap.

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 89%, so nearly every parameter is already documented in the schema, including the auto-detect behavior for repo/owner and the move_to_done/project_number dependency. The description contributes only a loose mapping of 'resolution' to resolution_notes and adds no new meaning beyond the structured fields.

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 names two concrete verbs and resources: close a GitHub issue and create a journal entry. The compound nature is explicit and cannot be inferred from the name alone, though it adds no differentiation from the mirror sibling create_github_issue_with_entry.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as closing an issue separately and calling update_entry or create_entry. The agent must infer that this tool is the right choice whenever a resolution should be journaled.

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