Skip to main content
Glama
dpesch

MantisBT MCP Server

by dpesch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Issue

get_issue
Read-onlyIdempotent

Fetch a single MantisBT issue by numeric ID, including notes, attachments, and relationships. Use select to limit fields and reduce response size.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric issue ID
selectNoComma-separated list of fields to include in the response (server-side projection, same as list_issues). Significantly reduces response size. Example: "id,summary,status,notes"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / id / maximum
      Added value: +9007199254740991
  2. Changed1 schema field changedv1.10.5
    • addedInput schema / properties / select
      Added value: +{
+  "description": "Comma-separated list of fields to include in the response (server-side projection, same as list_issues). Significantly reduces response size. Example: \"id,summary,status,notes\"",
+  "type": "string"
+}
  3. Addedv1.10.4
  4. Removed
  5. First observedv1.5.6

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive. The description adds genuinely useful behavior: notes, attachments, and relationships are included in the payload, and the select parameter can drop those fields. It doesn't mention pagination or response shape, but for a read tool this is solid added context.

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 short sentences, front-loaded with the core purpose, then the notable return behavior. Every sentence carries information with no waste.

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?

No output schema exists, so the description compensates by describing the returned contents (notes, attachments, relationships) and the effect of select. An agent has what it needs to call and interpret the 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 100%, so both id and select are already fully documented, including that select is a server-side projection reducing response size. The description only restates that select suppresses fields, adding little beyond the schema. Baseline 3.

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?

States a specific verb (Retrieve) and resource (a single MantisBT issue by numeric ID), and clarifies it is the singular counterpart to the list_issues/get_issues siblings. An agent can distinguish it from list_issues and list_notes without opening a schema.

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?

Clearly implies the fetch-one-issue context and explicitly routes the agent away from a separate list_notes call. It does not state exclusions or when to prefer get_issues over this tool, but the single-vs-list distinction is evident.

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

Deploy Server

Other Tools