Skip to main content
Glama

Delete Note

delete_note
DestructiveIdempotent

Permanently delete a note from a MantisBT issue. This action is irreversible and requires both issue ID and note ID.

Instructions

Permanently delete a note from a MantisBT issue. This action is irreversible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_idYesNumeric issue ID that owns the note
note_idYesNumeric note ID to delete

Implementation Reference

  • The async handler for the delete_note tool, which performs a DELETE request to the MantisBT API for the specified note.
      async ({ issue_id, note_id }) => {
        try {
          await client.delete<unknown>(`issues/${issue_id}/notes/${note_id}`);
          return {
            content: [{ type: 'text', text: `Note #${note_id} deleted from issue #${issue_id}.` }],
          };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: errorText(msg) }], isError: true };
        }
      }
    );
  • The registration of the delete_note tool with its schema definition using Zod.
    server.registerTool(
      'delete_note',
      {
        title: 'Delete Note',
        description: 'Permanently delete a note from a MantisBT issue. This action is irreversible.',
        inputSchema: z.object({
          issue_id: z.coerce.number().int().positive().describe('Numeric issue ID that owns the note'),
          note_id: z.coerce.number().int().positive().describe('Numeric note ID to delete'),
        }),
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: true,
        },
      },
Behavior4/5

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

The annotations declare destructiveHint=true and idempotentHint=true. The description reinforces this with 'Permanently' and 'irreversible,' adding valuable emphasis on the severity beyond the boolean flags. It does not, however, disclose additional behavioral traits like required permissions or side effects.

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 sentences efficiently convey the core action and critical safety warning. Every sentence earns its place with zero redundancy or filler.

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 two-parameter structure, clear annotations, and lack of output schema, the description adequately covers the essential context for a destructive operation. A minor gap remains regarding error conditions or return value details.

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 clearly documents that issue_id identifies the owning issue and note_id identifies the target. The description does not add parameter syntax, format details, or examples beyond the schema, warranting the baseline score.

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 states the specific action ('Permanently delete'), resource ('note'), and scope ('from a MantisBT issue'), clearly distinguishing it from siblings like delete_issue, detach_tag, or remove_relationship.

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 description warns that the action is 'irreversible,' providing implicit guidance about the severity and finality of the operation. However, it lacks explicit guidance on when to prefer this over alternatives (e.g., editing a note) or prerequisites (e.g., verifying the note exists via list_notes).

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