Skip to main content
Glama

get_issue

Retrieve the full details of a specific review issue by its issueSlugId (e.g. 'ISS-xxxxxx'), including title, description, status, targetSlugId, and comment thread. Set includeComments: false for a token-efficient summary when you only need the issue metadata.

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

Input Schema

NameRequiredDescriptionDefault
issueSlugIdYesUnique slug ID of the issue to retrieve (e.g. 'ISS-xxxxxx', obtained from list_issues, list_open_issues_for_mock, or user prompt).
includeCommentsNoWhether to include the full comment conversation history in the response. Set to false for token efficiency. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / includeComments / description
      Previous value: -"Set to false to omit full conversation comments for token efficiency. Default is true."New value: +"Whether to include the full comment conversation history in the response. Set to false for token efficiency. Defaults to true."
    • 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 retrieve (e.g. 'ISS-xxxxxx', obtained from list_issues, list_open_issues_for_mock, or user prompt)."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the response shape and the token-cost tradeoff of comment history, which is genuinely useful. It says nothing about error behavior for an invalid slug, permissions, or pagination of long comment threads, leaving gaps for a read tool with zero annotation coverage.

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 purpose followed by the cost-control hint; nothing is wasted. There is mild duplication with the schema descriptions, which keeps it from a 5.

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?

A simple two-parameter read tool with no output schema; the description compensates by enumerating the returned fields and flagging the expensive option. Only the absence of failure-mode guidance keeps it short of full completeness.

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 100%, so both parameters are already documented, and the description largely restates them (the 'ISS-xxxxxx' example and the token-efficiency rationale for includeComments). It adds the intent framing ('when you only need the issue metadata') but no new syntax or format detail, so baseline 3 applies.

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?

States a specific verb and resource ("Retrieve the full details of a specific review issue") and enumerates the fields returned (title, description, status, targetSlugId, comment thread). The word "specific" implicitly separates it from the list_* siblings, but no sibling is named explicitly.

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?

Gives one concrete usage rule: set includeComments to false when only metadata is needed. However, it never states when to prefer list_issues or list_open_issues_for_mock over this tool, nor what to do if the slug is unknown, so selection guidance is only implied.

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