triage-mcp

get_issue

Read-only

Retrieves a GitHub issue’s title, body, labels, assignees, author, state, and recent comments so coding agents can vet it before writing a fix.

Instructions

Get one issue: title, body (truncated if long), labels, assignees, author, state and the most recent comments.

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": {
      "repo": "<repo>",
      "number": "<number>"
    },
    "name": "get_issue"
  }
}

Input Schema

Name	Required	Description
`repo`	Yes
`number`	Yes
`commentLimit`	No	How many of the most recent comments to include

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond them: the body may be truncated if long, and only the most recent comments are included, which warns the agent that returned content may be partial. It does not mention total comment counts or pagination, so a 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that lists the returned fields with no filler or redundancy. The truncation caveat is attached inline to the field it affects rather than buried.

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?

With no output schema, the description appropriately enumerates the return shape (title, body, labels, assignees, author, state, comments) and flags truncation. It omits anything about error behavior for invalid repo/number, which is a minor remaining gap for a simple read tool.

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 only 33% — only commentLimit carries a schema description; repo and number are documented solely by name and a regex pattern. The description's phrase "the most recent comments" reinforces what commentLimit controls but never explains the owner/repo string format or the issue number semantics, so it only partially compensates.

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 opens with a specific verb+resource ("Get one issue") and enumerates exactly what is returned, so an agent can distinguish it from the plural search_issues sibling without opening the schema. It stops short of naming that sibling explicitly, which keeps it below a 5.

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 statement of when to prefer search_issues instead, and no prerequisites mentioned. The singular "one issue" implies a fetch-by-identifier use case, but the agent must infer that from the description rather than being told.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server