Skip to main content
Glama
dpesch

MantisBT MCP Server

by dpesch
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get MCP Server Version

get_mcp_version
Read-onlyIdempotent

Check the current version of the MantisBT MCP Server to verify compatibility and access available features for bug tracking integration.

Instructions

Returns the version of this mantisbt-mcp-server instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/version.ts:15-30 (registration)
    Tool registration and handler implementation for get_mcp_version.
    server.registerTool(
  'get_mcp_version',
  {
    title: 'Get MCP Server Version',
    description: 'Returns the version of this mantisbt-mcp-server instance.',
    inputSchema: z.object({}),
    annotations: {
      readOnlyHint: true,
      destructiveHint: false,
      idempotentHint: true,
    },
  },
  async () => ({
    content: [{ type: 'text', text: JSON.stringify({ version: mcpVersion }, null, 2) }],
  }),
);

Tool Definition Quality

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, establishing the safety profile. The description adds confirmation that this is a retrieval operation ('Returns'), but does not elaborate on return format, caching behavior, or performance characteristics.

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 description consists of a single, efficient sentence with nine words. It is front-loaded with the action and contains no redundancy or unnecessary prose.

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

Completeness4/5

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

Given the simplicity of the tool (zero parameters, simple string return implied by 'version'), the description is adequate. However, it could briefly note the expected return type or format (e.g., semantic version string) to be fully complete.

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

Parameters4/5

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

The tool accepts zero parameters, which establishes a baseline score of 4. The schema correctly defines an empty object with additionalProperties: false, and the description appropriately does not mention parameters since none exist.

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 ('Returns') and resource ('version of this mantisbt-mcp-server instance'), clearly indicating it retrieves the server version. It implicitly distinguishes from sibling 'get_mantis_version' by specifying 'mantisbt-mcp-server', though it could be more explicit about this distinction.

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 the similarly named sibling 'get_mantis_version', nor does it indicate typical usage scenarios (e.g., debugging, compatibility checks). No prerequisites or alternatives are mentioned.

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