Skip to main content
Glama

get_mantis_config

Retrieves MantisBT configuration options such as status and priority enums and workflows, enabling callers to use correct server values in bug-tracking operations.

Instructions

Gets configuration options from the MantisBT server (e.g. status_enum_string, priority_enum_string, workflows).

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": {
      "options": "<options>"
    },
    "name": "get_mantis_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsYesList of configuration keys (e.g. ['status_enum_string', 'priority_enum_string']).
user_idNo
project_idNo

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 provided, the description carries the full disclosure burden. 'Gets' implies a read, but it says nothing about authentication requirements, whether the call is safe or cached, or how user_id/project_id alter the returned values, and there is no output schema to fill the gap.

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; the parenthetical examples are the only substantive content and they add value, though they slightly duplicate the schema's example for `options`.

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?

The tool takes three parameters with optional user/project scoping, has no output schema, and has no annotations, so the description should explain the return shape (key/value map of configuration) and the effect of the scoping parameters. Neither is covered, leaving the agent under-informed for a non-trivial call.

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 coverage is only 33%: the `options` list is described in both schema and description, but user_id and project_id appear in the schema with no explanation anywhere. Those two parameters likely scope configuration resolution per user or project in MantisBT, which is meaningful behavior the description never mentions.

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 and resource (gets configuration options from the MantisBT server) and gives concrete examples of keys (status_enum_string, priority_enum_string, workflows), which pins down the domain well. It does not explicitly distinguish itself from siblings such as list_projects or get_project, but the config-resource focus makes the distinction fairly obvious.

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 when-to-use guidance: nothing says to call this before filtering issues by status, nor does it mention prerequisites, alternatives, or when it should be avoided. The agent must infer the use case entirely from the example keys.

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