Skip to main content
Glama
dpesch

MantisBT MCP Server

by dpesch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Project Versions

get_project_versions
Read-onlyIdempotent

List all versions for a MantisBT project, optionally including obsolete or inherited parent-project versions, to get valid names for issue version fields.

Instructions

List all versions defined for a MantisBT project. Returns an array of version objects, each containing id, name, released (boolean), obsolete (boolean), and timestamp (version date). To create, change, release or delete versions use create_version, update_version, release_version and delete_version.

Use the returned version names directly when creating or updating issues via create_issue and update_issue (version, target_version, fixed_in_version fields).

By default, obsolete and inherited parent-project versions are excluded. Set obsolete=true to include deprecated versions; set inherit=true to also return versions from parent projects.

Prerequisites: obtain project_id from list_projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inheritNoInclude versions inherited from parent projects. Default: false. Set to true for sub-projects that share versions with a parent project.
obsoleteNoInclude obsolete (deprecated) versions in the response. Default: false. Set to true to see all versions including those no longer actively used.
project_idYesNumeric project ID — use list_projects to discover project IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / project_id / maximum
      Added value: +9007199254740991
  2. Addedv1.10.4
  3. Removed
  4. Changed3 schema fields changedv1.10.3
    • changedInput schema / properties / inherit / description
      Previous value: -"Include versions inherited from parent projects (default: false)"New value: +"Include versions inherited from parent projects. Default: false. Set to true for sub-projects that share versions with a parent project."
    • changedInput schema / properties / obsolete / description
      Previous value: -"Include obsolete (deprecated) versions (default: false)"New value: +"Include obsolete (deprecated) versions in the response. Default: false. Set to true to see all versions including those no longer actively used."
    • changedInput schema / properties / project_id / description
      Previous value: -"Numeric project ID"New value: +"Numeric project ID — use list_projects to discover project IDs"
  5. First observedv1.5.6

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes beyond them by disclosing non-obvious default filtering behavior (obsolete and inherited parent versions excluded unless obsolete=true/inherit=true) and the shape of the returned objects. Lacks pagination/size notes, so not a full 5.

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 short paragraphs, front-loaded with the core action and scope before alternatives, flag behavior, and prerequisites. Every sentence carries new information; nothing is redundant filler.

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 read-only list tool with full schema coverage and annotations, this is complete: scope, default filtering, sibling routing, prerequisites, and return fields are all covered. No output schema exists, and the description compensates by naming the returned fields.

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 description coverage is 100%, so the defaults and meanings of obsolete/inherit/project_id are already documented. The description restates the default-filtering semantics and adds usage context for the returned names, but adds no syntax or format detail beyond the schema, so the baseline of 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?

Specific verb+resource ('List all versions defined for a MantisBT project') with the scope made explicit, and it names the create/change/release/delete sibling tools it is not. An agent can distinguish it from get_project_categories or list_projects 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 Guidelines5/5

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

Explicit routing: use create_version/update_version/release_version/delete_version for mutations, and a stated downstream use case (feed version names into create_issue/update_issue fields). It also states prerequisites (project_id from list_projects) and the flag conditions that change scope.

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