Skip to main content
Glama

add_note

Attach contextual information to task requests, enabling clear communication of project details, user preferences, or guidelines for reference during task execution.

Instructions

Add a note to a request. Notes can contain important information about the project, such as user preferences or guidelines.

Notes are displayed in the task progress table and can be referenced when working on tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestIdYes
titleYes
contentYes

Implementation Reference

  • Handler function for the 'add_note' tool that extracts requestId, title, and content from args and calls TaskFlowService.addNote
    async add_note(args: any) {
      const { requestId, title, content } = args ?? {};
      return service.addNote(String(requestId), String(title), String(content));
    },
  • Tool definition for 'add_note' including name, description, and input schema validation
    export const ADD_NOTE_TOOL: Tool = {
      name: "add_note",
      description:
        "Add a note to a request. Notes can contain important information about the project, such as user preferences or guidelines.\n\n" +
        "Notes are displayed in the task progress table and can be referenced when working on tasks.",
      inputSchema: {
        type: "object",
        properties: {
          requestId: { type: "string" },
          title: { type: "string" },
          content: { type: "string" },
        },
        required: ["requestId", "title", "content"],
      },
    };
  • Registration of ADD_NOTE_TOOL in the list of tools returned by ListToolsRequestHandler
    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 implements adding a note to a request: generates ID, sanitizes inputs, persists to file, and returns confirmation
    public async addNote(requestId: string, title: string, content: string) {
      await this.loadTasks();
      const req = this.getRequest(requestId);
      if (!req) return { status: "error", message: "Request not found" };
    
      const now = new Date().toISOString();
      const factory = new TaskFactory({ value: this.globalIdCounter });
      const noteId = factory.createNoteId();
      this.globalIdCounter = factory["counterRef"].value;
    
      const note: Note = {
        id: noteId,
        title: sanitizeString(title),
        content: sanitizeString(content),
        createdAt: now,
        updatedAt: now,
      };
    
      if (!req.notes) req.notes = [];
      req.notes.push(note);
      await this.saveTasks();
    
      return {
        status: "note_added",
        message: `Note "${title}" has been added to request ${requestId}.`,
        note,
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that notes are added and displayed/referenced, but lacks critical details such as required permissions, whether this is a mutation (implied by 'Add'), error conditions, or response format. This is a significant gap for a tool with no annotation coverage.

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?

The description is appropriately sized with two sentences that directly support the tool's purpose. The first sentence states the action and context, while the second explains the utility of notes. There is no wasted text, though it could be more front-loaded with key details.

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?

Given the complexity (3 parameters, no output schema, no annotations), the description is incomplete. It lacks details on parameter meanings, behavioral traits like permissions or side effects, and does not reference sibling tools. For a mutation tool with zero structured coverage, this is inadequate.

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 description coverage is 0%, so the description must compensate for undocumented parameters. It mentions notes contain 'important information about the project, such as user preferences or guidelines,' which loosely relates to 'content' but does not explain 'requestId' or 'title' parameters. This adds minimal value beyond the schema.

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 ('Add a note') and target resource ('to a request'), specifying that notes contain project information like user preferences or guidelines. However, it does not explicitly differentiate from sibling tools like 'update_note' or 'delete_note', which would require a 5.

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 mentions that notes are displayed in the task progress table and can be referenced when working on tasks, implying usage for tracking project details. However, it provides no explicit guidance on when to use this tool versus alternatives like 'update_note' or 'delete_note', nor any prerequisites or exclusions.

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