Skip to main content
Glama
Sign In
dpesch

MantisBT MCP Server

by dpesch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Project Versions

get_project_versions
Read-onlyIdempotent

Lists versions defined for a MantisBT project—excluding obsolete and inherited ones by default—so you can reference available version names when creating or updating issues.

Instructions

Deprecated: use get_project with include: ["versions"] instead — get_project_versions will be removed in 2.0.0.

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

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.7/5.0
Behavior5/5

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

Although annotations already declare this as read-only, idempotent, and non-destructive, the description adds substantial behavioral context: default exclusion of obsolete and inherited parent-project versions, the obsolete and inherit flags' effects, and the prerequisites for obtaining project_id. It also lists the returned version fields even though no output schema is provided.

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?

The deprecation notice is front-loaded, followed by purpose, return fields, related mutation tools, parameter behavior, and prerequisites. The structure is efficient and every paragraph contributes actionable information.

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?

Given that there is no output schema, the description compensates by listing the returned version object fields. It also covers prerequisites, default filtering behavior, and how the returned names map to issue creation and update 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 input schema already documents project_id, obsolete, and inherit fully. The description reinforces the default filtering behavior, but it largely repeats the schema's parameter documentation rather than adding new syntax or semantic detail beyond it.

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 states a specific verb and resource: listing all versions defined for a MantisBT project, and it names the replacement tool get_project with include: ["versions"]. It also distinguishes this read/list operation from version mutation siblings such as create_version and update_version.

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?

It explicitly says the tool is deprecated and should be replaced by get_project with include: ["versions"], while still explaining when to use the returned version names for create_issue and update_issue. It also gives clear alternatives for version mutation operations.

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