Skip to main content
Glama

Remove Issue Monitor

remove_monitor
Destructive

Remove a user from an issue's monitor list to stop email notifications for updates in MantisBT.

Instructions

Remove a user from the monitor list of a MantisBT issue. The user will no longer receive email notifications for updates to this issue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_idYesNumeric issue ID
usernameYesUsername of the monitor to remove

Implementation Reference

  • The implementation of the `remove_monitor` tool, including its schema, registration, and handler logic.
    server.registerTool(
      'remove_monitor',
      {
        title: 'Remove Issue Monitor',
        description: 'Remove a user from the monitor list of a MantisBT issue. The user will no longer receive email notifications for updates to this issue.',
        inputSchema: z.object({
          issue_id: z.coerce.number().int().positive().describe('Numeric issue ID'),
          username: z.string().min(1).describe('Username of the monitor to remove'),
        }),
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: false,
        },
      },
      async ({ issue_id, username }) => {
        try {
          await client.delete<unknown>(`issues/${issue_id}/monitors/${username}`);
          return {
            content: [{ type: 'text', text: JSON.stringify({ success: true }, null, 2) }],
          };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: errorText(msg) }], isError: true };
        }
      }
    );
Behavior3/5

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

The description adds valuable business context beyond annotations by stating the user-visible effect (email notifications stop), which explains what 'destructive' means in this context. However, it omits behavior details like idempotency considerations (despite idempotentHint=false), error cases, or permission requirements.

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 efficient sentences with no waste. Front-loaded with the action, followed by consequence. Every word earns its place.

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 simple 2-parameter schema, complete annotations, and straightforward destructive purpose, the description adequately covers the primary function and user impact. Minor gap: does not clarify behavior when removing a non-monitor user (relevant given idempotentHint=false).

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?

With 100% schema description coverage, the schema already fully documents both parameters (issue_id and username). The description references these concepts but does not add additional semantic detail, syntax guidance, or validation rules beyond the 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 uses specific verb 'Remove' with clear resource 'user from the monitor list of a MantisBT issue'. It implicitly distinguishes from sibling tools like add_monitor (opposite action) and delete_issue (different scope) by referencing the specific 'monitor list' resource.

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?

The second sentence explains the consequence (no more email notifications), implying when to use the tool, but lacks explicit 'when to use vs alternatives' guidance or mention of the inverse operation (add_monitor).

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