Skip to main content
Glama

Get MantisBT Configuration

get_config
Read-onlyIdempotent

Retrieve MantisBT configuration options like status, priority, severity, resolution, reproducibility, view state, and access level values for consistent issue tracking.

Instructions

Retrieve one or more MantisBT configuration options.

Common option names:

  • "status_enum_string" — issue status values and their IDs

  • "priority_enum_string" — priority values

  • "severity_enum_string" — severity values

  • "resolution_enum_string" — resolution values

  • "reproducibility_enum_string" — reproducibility values

  • "view_state_enum_string" — view state values

  • "access_levels_enum_string" — access level values

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
optionsYesArray of configuration option names to retrieve

Implementation Reference

  • The 'get_config' tool handler is defined and registered within the 'registerConfigTools' function in 'src/tools/config.ts'. It takes an array of configuration option names as input and retrieves them using the 'client.get' method.
      server.registerTool(
        'get_config',
        {
          title: 'Get MantisBT Configuration',
          description: `Retrieve one or more MantisBT configuration options.
    
    Common option names:
    - "status_enum_string" — issue status values and their IDs
    - "priority_enum_string" — priority values
    - "severity_enum_string" — severity values
    - "resolution_enum_string" — resolution values
    - "reproducibility_enum_string" — reproducibility values
    - "view_state_enum_string" — view state values
    - "access_levels_enum_string" — access level values`,
          inputSchema: z.object({
            options: z.array(z.string()).min(1).describe('Array of configuration option names to retrieve'),
          }),
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
          },
        },
        async ({ options }) => {
          try {
            const params: Record<string, string | number | boolean | undefined> = {};
            options.forEach((opt, i) => {
              params[`option[${i}]`] = opt;
            });
            const result = await client.get<unknown>('config', params);
            return {
              content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
            };
          } catch (error) {
            const msg = error instanceof Error ? error.message : String(error);
            return { content: [{ type: 'text', text: errorText(msg) }], isError: true };
          }
        }
      );
Behavior4/5

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

Annotations declare the operation as read-only and idempotent, which the description doesn't contradict. The description adds valuable behavioral context by listing concrete configuration option names, helping the agent understand what valid inputs look like and what data structure to expect.

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 is perfectly structured with a single declarative sentence followed by a bulleted list of examples. Every line earns its place; no redundant or tautological text.

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?

For a single-parameter retrieval tool, the description is nearly complete. The list of common option names provides the critical context needed for invocation. A minor gap is the lack of indication whether unknown option names error or return empty, but this is acceptable given the tool's simplicity.

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

Parameters5/5

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

While the schema has 100% coverage describing the 'options' array parameter, the description adds crucial semantic value by enumerating specific valid option names (e.g., 'status_enum_string') that the schema cannot provide. This compensates for the lack of enum constraints in the JSON schema.

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?

The description clearly states the tool retrieves 'MantisBT configuration options' with specific examples distinguishing it from issue-centric siblings like get_issue or get_metadata. The verb 'Retrieve' is precise and the resource scope is unambiguous.

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

Usage Guidelines4/5

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

The enumerated list of common option names (status_enum_string, priority_enum_string, etc.) provides excellent implicit guidance on valid use cases. However, it lacks explicit when-not-to-use guidance or differentiation from similar enum-retrieval tools like get_issue_enums.

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