Skip to main content
Glama

create_project_version

Creates a new version in a MantisBT project by specifying the project ID and version name, with optional release status, obsolete flag, date, and description.

Instructions

Creates a new version within a MantisBT project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "name": "<name>"
    },
    "name": "create_project_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
obsoleteNo
releasedNo
timestampNoVersion date in ISO-8601 format.
project_idYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only implies a mutation. It says nothing about required permissions, whether 'released'/'obsolete' default states have side effects, what happens on duplicate names, or what the call returns. This is thin for a write operation.

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?

A single front-loaded sentence with no filler or redundancy. Its brevity is a virtue structurally, even though the content is under-specified elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation tool with no annotations and no output schema, one sentence is far from sufficient. The agent lacks prerequisites, parameter meaning, side-effect disclosure, and return-value expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% (just the timestamp field), and the description compensates for none of the other five parameters. It implies a project scope and a version name but adds no meaning about 'released', 'obsolete', or 'description' beyond their bare property names.

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 states a specific verb and resource ('Creates a new version within a MantisBT project'), so an agent knows exactly what entity is produced. It does not distinguish itself from issue-oriented siblings like create_issue, but the resource 'version' is unambiguous enough that confusion is unlikely.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites such as the target project needing to exist, and no note on whether the version name must be unique within the project. The agent must infer all preconditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.