Skip to main content
Glama

check_mantis_connection

Validate connectivity and authentication with the MantisBT REST API, including automatic detection of the correct endpoint when mod_rewrite is disabled.

Instructions

Validates connectivity and authentication with the MantisBT REST API (including automatic detection of /api/rest/index.php when mod_rewrite is disabled).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_mantis_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses one non-obvious behavior (automatic detection of /api/rest/index.php when mod_rewrite is disabled), but it does not state whether the check is read-only, what happens on failure (exception vs. status object), or whether it has side effects or latency/auth prerequisites.

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?

One sentence, front-loaded with the core purpose, with the useful caveat in a parenthetical. No wasted wording; the mod_rewrite detail is niche but earns its place as behavioral context.

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

Completeness3/5

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

For a zero-parameter, zero-annotation diagnostic tool, the description should clarify what a caller receives (success/failure signal, error shape), since there is no output schema. That return-value information is missing, leaving a real gap.

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 takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly does not invent parameter discussion.

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?

States a specific verb ('validates') and a specific resource ('connectivity and authentication with the MantisBT REST API'), which no sibling tool covers. The purpose is unambiguous, though it does not explicitly contrast itself with any sibling operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is a pre-flight/diagnostic check before issue operations or after an auth failure, but the description never says when to call it or when not to. No alternatives or prerequisites (e.g., that credentials must already be configured) are mentioned.

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