Skip to main content
Glama
Sign In
dpesch

MantisBT MCP Server

by dpesch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Multiple Issues

get_issues
Read-onlyIdempotent

Fetch multiple MantisBT issues by numeric IDs in one parallel call, returning null for missing IDs and counters for requested, found, and failed.

Instructions

Deprecated: use get_issue with ids instead — get_issues will be removed in 2.0.0.

Retrieve multiple MantisBT issues by their numeric IDs in a single MCP call. Requests run in parallel (max 5 concurrent). Missing or inaccessible IDs return null at their array position — the call never fails due to individual missing IDs. Response includes "requested", "found", and "failed" counters for quick validation.

Input Schema

NameRequiredDescriptionDefault
idsYesArray of numeric issue IDs to fetch (1–50). null is returned per ID on 404/403/error instead of failing the whole call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / ids / items / maximum
      Added value: +9007199254740991
  2. Addedv1.10.4
  3. Removed
  4. Addedv1.5.15

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile, and the description adds genuinely new behavior: max 5 concurrent parallel requests, per-ID null on 404/403/error, and a guaranteed non-failing call. It also discloses the response shape ('requested', 'found', 'failed' counters) which is not derivable from annotations or schema.

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 plus a deprecation line, with the most important information (deprecation, then semantics) front-loaded. No filler and every sentence carries distinct content.

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, yet the description explains the array-with-nulls return shape and the counter fields, which is exactly what an agent needs to interpret results. Combined with the behavioral details, nothing essential is missing for a one-parameter read 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% and the single `ids` parameter is already fully documented, including the 1–50 bound and null-per-ID semantics. The description largely restates those facts rather than adding new parameter meaning, so baseline 3 applies.

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 and resource (retrieve multiple MantisBT issues by numeric IDs in a single call) and explicitly distinguishes itself from the singular sibling get_issue. The deprecation banner is front-loaded so the agent immediately knows the status of this 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?

Gives an explicit migration path — 'use get_issue with ids instead — get_issues will be removed in 2.0.0' — which tells the agent both when to use and when to avoid it. It doesn't discuss the batch-vs-single tradeoff or when batching 2–50 IDs is still preferable today, but the alternatives guidance is clear.

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