Skip to main content
Glama

Get Project Versions

get_project_versions
Read-onlyIdempotent

Retrieve all version information for a MantisBT project, including active, obsolete, and inherited versions, to manage project releases and track development milestones.

Instructions

List all versions defined for a MantisBT project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesNumeric project ID
obsoleteNoInclude obsolete (deprecated) versions (default: false)
inheritNoInclude versions inherited from parent projects (default: false)

Implementation Reference

  • Implementation of the 'get_project_versions' tool, which fetches versions for a specified MantisBT project.
    server.registerTool(
      'get_project_versions',
      {
        title: 'Get Project Versions',
        description: 'List all versions defined for a MantisBT project.',
        inputSchema: z.object({
          project_id: z.coerce.number().int().positive().describe('Numeric project ID'),
          obsolete: z.preprocess(coerceBool, z.boolean()).default(false).describe('Include obsolete (deprecated) versions (default: false)'),
          inherit: z.preprocess(coerceBool, z.boolean()).default(false).describe('Include versions inherited from parent projects (default: false)'),
        }),
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      async ({ project_id, obsolete, inherit }) => {
        try {
          const params: Record<string, number> = {};
          if (obsolete) params.obsolete = 1;
          if (inherit) params.inherit = 1;
          const result = await client.get<{ versions: MantisVersion[] }>(`projects/${project_id}/versions`, params);
          return {
            content: [{ type: 'text', text: JSON.stringify(result.versions ?? result, null, 2) }],
          };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: errorText(msg) }], isError: true };
        }
      }
    );
Behavior3/5

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

Annotations already declare the operation as read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds minimal behavioral context beyond stating it lists 'all versions,' failing to explain what constitutes a version in MantisBT (e.g., product releases), pagination behavior, or return format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no redundant words. While appropriately front-loaded, it borders on underspecification—lacking even a brief mention of return value or usage context that would help an agent confirm this is the right tool before invocation.

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?

Given the simple input schema (3 primitive parameters with 100% coverage) and presence of safety annotations, the description is minimally adequate. However, with no output schema provided, the description misses the opportunity to clarify what data structure or version attributes (name, date, status) will be returned.

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 fully documents all three parameters (project_id, obsolete, inherit) including their types, defaults, and purposes. The description adds no additional semantic information beyond the schema, warranting the baseline score for high-coverage schemas.

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?

The description uses a specific verb ('List') and resource ('versions'), clearly indicating it retrieves version data for a MantisBT project. However, it does not explicitly differentiate from siblings like 'get_project_categories' or 'get_project_users', relying solely on the resource name 'versions' to distinguish its function.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a valid project_id from list_projects), nor does it clarify when to use the 'obsolete' or 'inherit' flags versus retrieving only active versions.

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