Skip to main content
Glama

get_issue_full_context

Retrieves complete details for a MantisBT issue by ID, including description, notes, history, attachments, custom fields, and relationships so you can inspect and act on full issue context.

Instructions

Gets all details of a specific issue by ID (description, notes, history, attachments, custom fields and relationships).

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": {
      "issue_id": "<issue_id>"
    },
    "name": "get_issue_full_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYesIssue ID in MantisBT.
include_historyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 burden. It usefully discloses the returned data scope (description, notes, history, attachments, custom fields, relationships), but does not state read-only safety, permissions, or how include_history changes behavior.

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 with no filler; the parenthetical list efficiently enumerates returned fields. It is appropriately sized for a simple getter.

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?

The description covers the main return contents, which helps because no output schema exists. However, with no annotations, an undescribed include_history parameter, and no usage guidance, it is only minimally complete for an agent to invoke it confidently.

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?

Schema coverage is 50%; issue_id is described in the schema, but include_history has no schema description and the tool description never explains the boolean toggle or its default. With half the parameters undocumented, the description does not compensate for the schema gap.

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 ('Gets') and resource ('specific issue by ID'), and enumerates the detail categories returned. It does not explicitly differentiate from siblings such as get_issue_attachment or list_issues, so it stops short of 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?

Provides no when-to-use guidance, prerequisites, or alternatives. An agent can infer this is for full issue context, but there is no explicit routing against list_issues, search_vector_issues, or get_issue_attachment.

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