Skip to main content
Glama

delete_note

Remove a specific note from a task request in TaskFlow MCP by providing the request ID and note ID.

Instructions

Delete a note from a request.

Provide the 'requestId' and 'noteId' of the note to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestIdYes
noteIdYes

Implementation Reference

  • The main handler function for the 'delete_note' tool. Extracts requestId and noteId from arguments and calls the TaskFlowService.deleteNote method.
    async delete_note(args: any) {
      const { requestId, noteId } = args ?? {};
      return service.deleteNote(String(requestId), String(noteId));
    },
  • JSON Schema definition for the 'delete_note' tool input validation.
    delete_note: {
      type: "object",
      properties: {
        requestId: { type: "string" },
        noteId: { type: "string" },
      },
      required: ["requestId", "noteId"],
    },
  • Registration of the 'delete_note' tool (DELETE_NOTE_TOOL) in the server's list of available tools.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        PLAN_TASK_TOOL,
        GET_NEXT_TASK_TOOL,
        MARK_TASK_DONE_TOOL,
        OPEN_TASK_DETAILS_TOOL,
        LIST_REQUESTS_TOOL,
        ADD_TASKS_TO_REQUEST_TOOL,
        UPDATE_TASK_TOOL,
        DELETE_TASK_TOOL,
        ADD_SUBTASKS_TOOL,
        MARK_SUBTASK_DONE_TOOL,
        UPDATE_SUBTASK_TOOL,
        DELETE_SUBTASK_TOOL,
        EXPORT_TASK_STATUS_TOOL,
        ADD_NOTE_TOOL,
        UPDATE_NOTE_TOOL,
        DELETE_NOTE_TOOL,
        ADD_DEPENDENCY_TOOL,
        GET_PROMPTS_TOOL,
        SET_PROMPTS_TOOL,
        UPDATE_PROMPTS_TOOL,
        REMOVE_PROMPTS_TOOL,
        ARCHIVE_COMPLETED_REQUESTS_TOOL,
        LIST_ARCHIVED_REQUESTS_TOOL,
        RESTORE_ARCHIVED_REQUEST_TOOL,
      ],
    }));
  • Core service method that performs the note deletion logic: loads data, finds the note, removes it from the request's notes array, and saves the changes.
    public async deleteNote(requestId: string, noteId: string) {
      await this.loadTasks();
      const req = this.getRequest(requestId);
      if (!req) return { status: "error", message: "Request not found" };
    
      if (!req.notes) return { status: "error", message: "No notes found for this request" };
    
      const noteIndex = req.notes.findIndex((n) => n.id === noteId);
      if (noteIndex === -1) return { status: "error", message: "Note not found" };
    
      req.notes.splice(noteIndex, 1);
      await this.saveTasks();
    
      return { status: "note_deleted", message: `Note ${noteId} has been deleted.` };
    }
  • Initialization of handlers object which includes the delete_note handler function from taskflowHandlers.
    this.handlers = taskflowHandlers(service);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive operation, it doesn't specify whether this is permanent, reversible, requires specific permissions, or has side effects. The description lacks critical behavioral context for a destructive operation.

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 extremely concise with two sentences that directly address the tool's purpose and parameter requirements. Every word serves a clear purpose with zero wasted text, making it easy to parse quickly.

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?

For a destructive operation with no annotations, no output schema, and 0% schema description coverage, the description is insufficient. It doesn't address the permanence of deletion, error conditions, authorization requirements, or what happens to related data, leaving significant gaps in understanding.

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?

The description mentions both parameters ('requestId' and 'noteId') and their purpose ('of the note to delete'), but with 0% schema description coverage, it doesn't provide format details, constraints, or examples. It adds basic semantic meaning but doesn't fully compensate for the complete lack of schema documentation.

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?

The description clearly states the action ('Delete') and target ('a note from a request'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'delete_subtask' or 'delete_task', which also perform deletion operations on different resources.

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?

The description provides no guidance on when to use this tool versus alternatives like 'update_note' or other deletion tools. It doesn't mention prerequisites, consequences, or any context about when deletion is appropriate versus modification.

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/pinkpixel-dev/taskflow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server