Skip to main content
Glama
108yen
by 108yen

Create Memo

createMemo

Create and store memos with titles and content using a local database for agents to record and manage information.

Instructions

Create a new memo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryIdNo
contentYes
titleYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
memoYes

Implementation Reference

  • Core handler function that creates a new memo: generates ID with nanoid, adds timestamps, appends to in-memory DB, and persists it.
    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
    }
  • Zod schema defining the input structure for createMemo: title (string), content (string), optional categoryId (string).
    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 with the MCP server, providing schema, description, and a thin handler that delegates to the core createMemo function and formats the MCP response.
    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 },
        }
      },
    )
Behavior1/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. 'Create a new memo' implies a write operation but reveals nothing about permissions needed, whether creation is idempotent, what happens on duplicate titles, error conditions, or response format. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral transparency.

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 at three words, with zero wasted language. It's front-loaded with the core action ('Create'), though this brevity comes at the cost of completeness. Every word earns its place by directly stating the tool's function without redundancy.

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 tool's complexity (a write operation with 3 parameters, 2 required), lack of annotations, and 0% schema description coverage, the description is incomplete. While an output schema exists (which reduces the need to explain return values), the description doesn't address critical aspects like behavioral traits, parameter meanings, or usage context, leaving significant gaps for agent understanding.

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%, meaning none of the three parameters (categoryId, content, title) are documented in the schema. The description adds no parameter information beyond what's inferred from the tool name—it doesn't explain what these parameters mean, their formats, or relationships. This fails to compensate for the schema's lack of descriptions.

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

Purpose2/5

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

The description 'Create a new memo' is a tautology that essentially restates the tool name and title without adding meaningful specificity. It doesn't distinguish this tool from sibling tools like 'createCategory' or explain what a 'memo' is in this context. While the verb 'create' is clear, the resource 'memo' remains undefined, making this minimally informative.

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?

The description provides no guidance on when to use this tool versus alternatives. There are multiple sibling tools (e.g., updateMemo, getMemo, searchMemos) that handle memos differently, but the description doesn't indicate that this is for initial creation versus modification or retrieval. No prerequisites, exclusions, or contextual recommendations 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