Skip to main content
Glama
108yen
by 108yen

Create Memo

createMemo

Create a memo with a title and content, optionally specifying a category. Records the memo in a local database for later retrieval.

Instructions

Create a new memo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryIdNo
contentYes
titleYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
memoYes

Implementation Reference

  • The actual handler function that creates a memo. It takes a CreateMemo object, assigns it an ID via nanoid, sets createdAt/updatedAt timestamps, pushes it to the db, writes, and returns the new memo.
    export const createMemo = async (memo: CreateMemo) => {
      const now = new Date().toISOString()
    
      const newMemo = {
        ...memo,
        createdAt: now,
        id: nanoid(),
        updatedAt: now,
      }
      db.data.memos.push(newMemo)
      await db.write()
    
      return newMemo
    }
  • CreateMemoSchema defines the input validation schema for creating a memo (categoryId optional, content required, title required). CreateMemo is the inferred TypeScript type.
    export const CreateMemoSchema = z.object({
      categoryId: z.string().optional(),
      content: z.string(),
      title: z.string(),
    })
    
    export type CreateMemo = z.infer<typeof CreateMemoSchema>
  • Registers the 'createMemo' tool on the MCP server with metadata (description, inputSchema, outputSchema, title) and the handler that calls createMemo and returns structured content.
    export function registerTools(server: McpServer) {
      server.registerTool(
        "createMemo",
        {
          description: "Create a new memo",
          inputSchema: CreateMemoSchema.shape,
          outputSchema: { memo: MemoSchema },
          title: "Create Memo",
        },
        async (memo) => {
          const newMemo = await createMemo(memo)
          return {
            content: [{ text: JSON.stringify(newMemo), type: "text" }],
            structuredContent: { memo: newMemo },
          }
        },
      )
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'Create' implying mutation, but fails to disclose behaviors such as required permissions, id generation, error conditions, or any 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.

Conciseness2/5

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

The description is only one short sentence, which is concise but severely under-specified. It lacks structure and fails to provide helpful information for an AI agent.

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 presence of an output schema, return values are not required. However, the description omits essential context such as validation rules, default values for optional parameters, and behavior when required fields are missing. It is incomplete for a mutation tool with no annotations.

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?

Input schema has 3 parameters with 0% description coverage, and the tool description adds no explanation. The description does not clarify the meaning, constraints, or usage patterns for categoryId, content, or title beyond their type and requirement status.

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 'Create a new memo' clearly states the verb and resource, matching the tool name. It is unambiguous but does not add any additional context to differentiate from sibling tools like createCategory or updateMemo beyond the tool name itself.

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 such as updateMemo, deleteMemo, or searchMemos. No prerequisites or conditions are mentioned.

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/108yen/memo-mcp'

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