Skip to main content
Glama
108yen
by 108yen

Delete Memo

deleteMemo

Remove a specific memo from the memo-mcp server by providing its unique ID to clear stored information.

Instructions

Delete a memo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the memo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
memoYes

Implementation Reference

  • MCP tool handler for 'deleteMemo' that invokes the repository function, handles cases where memo is not found, and returns formatted text and structured content.
    async ({ id }) => {
      const deletedMemo = await deleteMemo(id)
      if (!deletedMemo) {
        return {
          content: [{ text: "Memo not found", type: "text" }],
          isError: true,
        }
      }
    
      return {
        content: [{ text: JSON.stringify(deletedMemo), type: "text" }],
        structuredContent: { memo: deletedMemo },
      }
    },
  • Input and output schema definition for the deleteMemo tool, specifying id parameter and memo output.
    {
      description: "Delete a memo",
      inputSchema: {
        id: z.string().describe("The ID of the memo"),
      },
      outputSchema: { memo: MemoSchema },
      title: "Delete Memo",
    },
  • Registration of the 'deleteMemo' tool on the MCP server using server.registerTool.
    server.registerTool(
      "deleteMemo",
      {
        description: "Delete a memo",
        inputSchema: {
          id: z.string().describe("The ID of the memo"),
        },
        outputSchema: { memo: MemoSchema },
        title: "Delete Memo",
      },
      async ({ id }) => {
        const deletedMemo = await deleteMemo(id)
        if (!deletedMemo) {
          return {
            content: [{ text: "Memo not found", type: "text" }],
            isError: true,
          }
        }
    
        return {
          content: [{ text: JSON.stringify(deletedMemo), type: "text" }],
          structuredContent: { memo: deletedMemo },
        }
      },
    )
  • Repository helper function that performs the actual deletion of a memo by ID from the in-memory database and returns the deleted memo.
    export const deleteMemo = async (id: string) => {
      await db.read()
    
      const index = db.data.memos.findIndex((memo) => memo.id === id)
      if (index == -1) {
        return undefined
      }
    
      const [deletedMemo] = db.data.memos.splice(index, 1)
      await db.write()
      return deletedMemo
    }
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. 'Delete a memo' implies a destructive mutation, but it doesn't specify whether deletion is permanent or reversible, what permissions are required, if there are rate limits, or what happens on success/failure. For a destructive tool with zero annotation coverage, this is a critical gap that leaves the agent uninformed about risks and outcomes.

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 text. It's front-loaded with the core action ('Delete'), though this brevity comes at the cost of completeness. Every word earns its place by stating the essential operation, making it structurally efficient despite its informational shortcomings.

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 destructive mutation with no annotations) and the presence of an output schema (which handles return values), the description is incomplete. It fails to address critical context like behavioral traits, usage guidelines, or safety considerations, leaving significant gaps for an agent to operate effectively. The output schema mitigates some issues but doesn't compensate for the lack of guidance in the description itself.

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

Parameters3/5

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

The description adds no parameter information beyond what the input schema provides. However, schema description coverage is 100% (the 'id' parameter is fully documented in the schema), and there's only one parameter, so the baseline score is 3. The description doesn't compensate for any gaps, but none exist given the high schema coverage and minimal parameter count.

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 'Delete a memo' is a tautology that restates the tool name/title without adding specificity. While it clearly identifies the verb ('Delete') and resource ('memo'), it doesn't distinguish this tool from its sibling 'deleteCategory' or explain what constitutes a 'memo' versus other resources. This is minimal information that barely exceeds a 1 (tautology) but lacks the differentiation needed for higher scores.

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. It doesn't mention prerequisites (e.g., needing an existing memo ID), exclusions, or relationships with sibling tools like 'getMemo' for verification or 'updateMemo' for modification. With multiple sibling tools present, this absence of context is misleading for an agent trying to select the correct operation.

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