Skip to main content
Glama

get_issue

Fetches complete details for a single issue by number, including any linked tab text, so agents can review and act on specific items.

Instructions

한 건 전체(자르지 않음) + '연결탭'이 있으면 그 탭의 텍스트.

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

Input Schema

NameRequiredDescriptionDefault
noYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two real traits beyond the schema — the record is returned untruncated, and linked-tab text is appended only when such a tab exists — which is more than most one-liners add. It says nothing about permissions, failure modes, or size limits for an operation that could return large bodies.

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

Conciseness3/5

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

It is a single compact line with no wasted filler, and the 'not truncated' qualifier is placed up front. However, the phrasing is cryptic, mixing a parenthetical negation with a conditional clause, which costs more in clarity than it saves in length.

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?

An output schema exists, so return values need not be explained, and the description covers the shape of the result. But for a lookup tool whose sole identifier is undocumented in both schema and prose, and with no annotations, the definition leaves an agent guessing at the most important input.

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?

There is one required parameter, 'no', at 0% schema description coverage, so the description must explain it. It never mentions the parameter at all — an agent must guess that 'no' is the issue number and not a count or offset. The phrase '한 건' hints at a single-record selector but adds no explicit meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys the gist of a single-record fetch that returns the whole record without truncation, plus text from a 'linked tab' when one exists. But it never states the resource (issue) or a clean verb, so an agent must infer from the tool name that it fetches one issue by number rather than something else.

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?

No when-to-use or when-not guidance is given. The 'not truncated' hint implies a contrast with list_issues, but no alternative is named and no prerequisite is stated, so routing between get_issue and its siblings is left entirely to inference.

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