Skip to main content
Glama

Get Issue

get_issue
Read-onlyIdempotent

Retrieve a complete MantisBT issue by its ID, including all fields, notes, attachments, and relationships in a single call.

Instructions

Retrieve a single MantisBT issue by its numeric ID. Returns all issue fields including notes, attachments, and relationships. Notes are always included — no separate list_notes call needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric issue ID

Implementation Reference

  • The `get_issue` tool registration and handler implementation.
    server.registerTool(
      'get_issue',
      {
        title: 'Get Issue',
        description: 'Retrieve a single MantisBT issue by its numeric ID. Returns all issue fields including notes, attachments, and relationships. Notes are always included — no separate list_notes call needed.',
        inputSchema: z.object({
          id: z.coerce.number().int().positive().describe('Numeric issue ID'),
        }),
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      async ({ id }) => {
        try {
          const result = await client.get<{ issues: MantisIssue[] }>(`issues/${id}`);
          const issue = result.issues?.[0] ?? result;
          return {
            content: [{ type: 'text', text: JSON.stringify(issue, null, 2) }],
          };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: errorText(msg) }], isError: true };
        }
      }
    );
Behavior4/5

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

Annotations declare read-only/idempotent safety profile. Description adds valuable behavioral context: 'Returns all issue fields including notes, attachments, and relationships' and 'Notes are always included' — disclosing data richness and inclusion behavior not captured in annotations. No contradiction with safety hints.

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?

Three sentences with zero waste: sentence 1 defines action, sentence 2 describes return payload, sentence 3 provides optimization guidance. Front-loaded with core purpose. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read operation, description adequately covers the parameter, return value structure (fields, notes, attachments, relationships), and behavioral quirks. Annotations handle safety characteristics. Complete despite lack of output schema.

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 has 100% coverage with 'Numeric issue ID' describing the id parameter. Description references 'numeric ID' reinforcing the parameter usage, but with complete schema coverage, the description adds minimal semantic detail beyond what structured data provides. Baseline 3 appropriate.

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

Purpose5/5

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

Description opens with 'Retrieve a single MantisBT issue by its numeric ID' providing specific verb (Retrieve), resource (MantisBT issue), and scope (single/by ID). The 'single' qualifier distinguishes it from sibling get_issues, and the note about list_notes further differentiates it from that sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'no separate list_notes call needed' — clear when-not guidance naming the sibling alternative. This prevents redundant API calls. Could improve by explicitly contrasting with get_issues for bulk vs single retrieval, but the 'single' qualifier provides implicit guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dpesch/mantisbt-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server