Skip to main content
Glama

Get Multiple Issues

get_issues
Read-onlyIdempotent

Retrieve multiple MantisBT issues by their numeric IDs in a single call, with parallel processing and graceful handling of missing or inaccessible IDs.

Instructions

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

TableJSON 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.

Implementation Reference

  • The implementation of the get_issues tool, which retrieves multiple MantisBT issues by their numeric IDs concurrently.
    server.registerTool(
      'get_issues',
      {
        title: 'Get Multiple Issues',
        description:
          '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.',
        inputSchema: z.object({
          ids: z
            .array(z.coerce.number().int().positive())
            .min(1)
            .max(50)
            .describe('Array of numeric issue IDs to fetch (1–50). null is returned per ID on 404/403/error instead of failing the whole call.'),
        }),
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      async ({ ids }) => {
        const results = await runWithConcurrency(
          ids,
          GET_ISSUES_CONCURRENCY,
          async (id): Promise<MantisIssue | null> => {
            try {
              const result = await client.get<{ issues: MantisIssue[] }>(`issues/${id}`);
              return result.issues?.[0] ?? (result as unknown as MantisIssue);
            } catch {
              return null;
            }
          },
        );
        const found = results.filter((r) => r !== null).length;
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(
              { issues: results, requested: ids.length, found, failed: ids.length - found },
              null,
              2,
            ),
          }],
        };
      },
    );
Behavior5/5

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

The description adds substantial behavioral context beyond annotations: it discloses parallel execution constraints ('max 5 concurrent'), critical error handling semantics ('call never fails due to individual missing IDs'), and response structure ('requested', 'found', and 'failed' counters). This compensates perfectly for the lack of output 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?

Four sentences total, front-loaded with purpose. Every sentence earns its place: sentence 1 states purpose, sentence 2 discloses concurrency limits, sentence 3 explains fault tolerance, and sentence 4 describes return metadata. No redundancy or 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?

Despite having no output schema, the description adequately covers the return structure through explicit mention of counters and null positioning. Combined with clear annotations (readOnly/idempotent) and comprehensive parameter documentation, the description provides sufficient context for correct invocation and response handling.

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?

With 100% schema description coverage, the schema already fully documents the ids parameter including array constraints and null-return behavior. The description reinforces the 'numeric IDs' aspect but does not add syntax details, examples, or semantic clarification beyond what the structured schema provides, meeting the baseline expectation.

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?

The description opens with a specific verb ('Retrieve') + resource ('MantisBT issues') + method ('by their numeric IDs in a single MCP call'). It clearly distinguishes this batch operation from sibling tools like get_issue (singular) and list_issues (filter-based), establishing the exact scope and purpose.

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?

The phrase 'in a single MCP call' implies efficiency through batching versus multiple individual calls, suggesting when to use this tool (bulk ID retrieval). However, it does not explicitly name alternatives like get_issue or differentiate from list_issues for search scenarios, stopping short of explicit when-to-use 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