Skip to main content
Glama
Sign In
dpesch

MantisBT MCP Server

by dpesch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get MantisBT Version

get_mantis_version
Read-onlyIdempotent

Retrieve the version of the connected MantisBT installation and optionally compare it with the official GitHub release to check for updates.

Instructions

Deprecated: use get_version instead — get_mantis_version will be removed in 2.0.0.

Returns the version of the connected MantisBT installation and optionally compares it against the latest official release on GitHub.

Input Schema

NameRequiredDescriptionDefault
check_latestNoWhether to fetch the latest MantisBT release from GitHub and compare (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.0
    • changedInput schema / properties / check_latest / description
      Previous value: -"Whether to fetch the latest release from GitHub and compare (default: true)"New value: +"Whether to fetch the latest MantisBT release from GitHub and compare (default: true)"
  2. Changed1 schema field changedv1.14.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Addedv1.10.4
  4. Removed
  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 readOnly/idempotent/non-destructive, and the description adds meaningful context beyond them: the tool may reach out to GitHub for the latest official release when comparing, which is a side effect an agent should know about. It does not describe the shape of the returned version data, but no output schema exists to cover that gap either.

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?

Two sentences, deprecation warning front-loaded before any functional detail, zero filler. The most decision-relevant fact appears first.

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 one-parameter read-only tool with full annotation coverage, the definition supplies everything needed: deprecation status, migration target, purpose, and the optional network-dependent comparison behavior.

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% and the single boolean parameter check_latest is fully documented there. The description's phrase 'optionally compares' mirrors that but adds no format or default detail, so baseline 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?

States a specific verb (returns) and resource (version of the connected MantisBT installation), plus the optional GitHub comparison. It also names the sibling get_version as its replacement, so an agent can distinguish it from get_version and get_mcp_version without opening any 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?

Explicitly marks the tool deprecated, names the alternative (get_version) and gives the removal timeline (2.0.0). This is a textbook when-not-to-use-this / use-that-instead instruction.

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