Skip to main content
Glama
jasonkneen

Simple TypeScript MCP Server

by jasonkneen

updateNote

Modify existing notes by updating their title and content using the note ID. This tool helps maintain accurate and current information in your note-taking system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteIdYesThe ID of the note to update
titleNoThe updated title of the note
contentNoThe updated content of the note

Implementation Reference

  • Handler function for the 'updateNote' MCP tool that validates input, calls the notes store update method, handles note not found and errors, and returns a standardized JSON text response.
    async ({ noteId, title, content }) => {
      try {
        const updatedNote = notesStore.updateNote(noteId, { title, content });
        
        if (!updatedNote) {
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  success: false,
                  error: "Note not found",
                  noteId
                }, null, 2)
              }
            ]
          };
        }
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: true,
                note: updatedNote
              }, null, 2)
            }
          ]
        };
      } catch (err) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: false,
                error: "Failed to update note",
                noteId
              }, null, 2)
            }
          ]
        };
      }
    },
  • Zod input schema for the 'updateNote' tool defining required noteId and optional title/content parameters.
    {
      noteId: z.string().describe("The ID of the note to update"),
      title: z.string().optional().describe("The updated title of the note"),
      content: z.string().optional().describe("The updated content of the note")
    },
  • Core helper method in NotesStore class that performs the actual note update logic by mutating the in-memory note object if it exists.
    updateNote(id: string, updates: { title?: string; content?: string }): Note | undefined {
      const note = this.notes[id];
      
      if (!note) {
        return undefined;
      }
    
      if (updates.title !== undefined) {
        note.title = updates.title;
      }
    
      if (updates.content !== undefined) {
        note.content = updates.content;
      }
      
      return note;
    }
  • TypeScript interface defining the structure of a Note object, used in the updateNote method and responses.
    export interface Note {
      id: string;
      title: string;
      content: string;
      createdAt: string;
    }
  • src/server.ts:139-191 (registration)
    MCP server.tool registration for the 'updateNote' tool, specifying name, input schema, and inline handler function.
    server.tool(
      "updateNote",
      {
        noteId: z.string().describe("The ID of the note to update"),
        title: z.string().optional().describe("The updated title of the note"),
        content: z.string().optional().describe("The updated content of the note")
      },
      async ({ noteId, title, content }) => {
        try {
          const updatedNote = notesStore.updateNote(noteId, { title, content });
          
          if (!updatedNote) {
            return {
              content: [
                {
                  type: "text",
                  text: JSON.stringify({
                    success: false,
                    error: "Note not found",
                    noteId
                  }, null, 2)
                }
              ]
            };
          }
          
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  success: true,
                  note: updatedNote
                }, null, 2)
              }
            ]
          };
        } catch (err) {
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  success: false,
                  error: "Failed to update note",
                  noteId
                }, null, 2)
              }
            ]
          };
        }
      },
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/jasonkneen/mcp-server-ts'

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