Skip to main content
Glama

Get GitHub Issue Details

get_github_issue
Read-onlyIdempotent

Retrieve detailed information about a specific GitHub issue, auto-detecting the repository from git and optionally limiting body text or comments to reduce token usage.

Instructions

Get detailed information about a specific GitHub issue. IMPORTANT: Do NOT guess owner/repo values - leave them empty to auto-detect from the current git repository.

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": "get_github_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoLEAVE EMPTY to auto-detect from git
ownerNoLEAVE EMPTY to auto-detect from git
use_test_dbNo
issue_numberNo
truncate_bodyNoMax characters for body text (0 = full body, default 800). Reduces token usage.
include_commentsNoInclude issue comments (default false). Each comment adds tokens.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds one genuinely useful operational trait, that owner/repo resolve from the current git repository rather than being supplied, but says nothing about pagination, comment volume, or failure behavior when no git repo is present.

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 sentences, front-loaded with the purpose and then the high-value caveat. The capitalized IMPORTANT is a reasonable emphasis choice for an error agents commonly make. Nothing is redundant, though the second sentence is a schema paraphrase rather than new information.

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?

An output schema exists, so return-value explanation is not required, and the tool is a simple read with no mutation risk. The gaps are modest: use_test_db has no meaning anywhere, and the description does not note whether issue_number is effectively mandatory despite zero required parameters.

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 67%, so the schema already documents repo, owner, truncate_body and include_comments with defaults and token implications. The description merely echoes the auto-detect guidance for owner/repo and leaves issue_number and use_test_db, the latter documented nowhere, entirely unexplained; baseline 3 fits given the schema does most of the work.

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 uses a specific verb and resource ('Get detailed information about a specific GitHub issue'), which cleanly separates it from the plural sibling get_github_issues. It does not name that sibling explicitly, but the singular/plural contrast plus 'detailed' makes the distinction clear enough without opening a schema.

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?

There is no explicit when-to-use guidance and no named alternative, so the agent must infer that this is the single-issue lookup versus get_github_issues for listing. The one strong usage instruction present is the 'Do NOT guess owner/repo' warning, which is operational rather than routing guidance.

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