Skip to main content
Glama
jasonkneen

Simple TypeScript MCP Server

by jasonkneen

createNote

Create and store notes with titles and content using a TypeScript MCP server for note-taking operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesThe title of the note
contentYesThe content of the note

Implementation Reference

  • The handler function for the 'createNote' MCP tool. It takes title and content, calls notesStore.createNote, and returns a JSON response with the new note or an error.
      async ({ title, content }) => {
        try {
          const newNote = notesStore.createNote(title, content);
          
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  success: true,
                  note: newNote
                }, null, 2)
              }
            ]
          };
        } catch (err) {
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  success: false,
                  error: "Failed to create note"
                }, null, 2)
              }
            ]
          };
        }
      },
    );
  • Input schema for the createNote tool using Zod, defining required string parameters for title and content.
    {
      title: z.string().describe("The title of the note"),
      content: z.string().describe("The content of the note")
    },
  • src/server.ts:101-136 (registration)
    Registration of the 'createNote' tool on the MCP server, including name, input schema, and handler function.
    server.tool(
      "createNote",
      {
        title: z.string().describe("The title of the note"),
        content: z.string().describe("The content of the note")
      },
      async ({ title, content }) => {
        try {
          const newNote = notesStore.createNote(title, content);
          
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  success: true,
                  note: newNote
                }, null, 2)
              }
            ]
          };
        } catch (err) {
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  success: false,
                  error: "Failed to create note"
                }, null, 2)
              }
            ]
          };
        }
      },
    );
  • Helper method in NotesStore class that creates a new Note object with generated ID and stores it in memory.
    createNote(title: string, content: string): Note {
      const id = `note${Date.now()}`;
      const newNote = {
        id,
        title,
        content,
        createdAt: new Date().toISOString()
      };
      
      this.notes[id] = newNote;
      return newNote;
    }
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