Skip to main content
Glama
108yen
by 108yen

Get Memos

getMemos

Retrieve all stored memos from the local database to review previously recorded information.

Instructions

Get all memos

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
memosYes

Implementation Reference

  • The actual handler function that reads the database and returns all memos.
    export const getMemos = async () => {
      await db.read()
      return db.data.memos
    }
  • The tool registration on the MCP server, mapping the name 'getMemos' to the handler.
    server.registerTool(
      "getMemos",
      {
        description: "Get all memos",
        inputSchema: {},
        outputSchema: { memos: z.array(MemoSchema) },
        title: "Get Memos",
      },
      async () => {
        const memos = await getMemos()
        return {
          content: [{ text: JSON.stringify(memos), type: "text" }],
          structuredContent: { memos },
        }
      },
    )
  • The MemoSchema (Zod) used as the output schema for the memos returned by getMemos.
    export const MemoSchema = z.object({
      categoryId: z.string().optional(),
      content: z.string(),
      createdAt: z
        .string()
        .datetime()
        .transform((date) => new Date(date))
        .describe(
          "The date when the memo was created. Display in ISO 8601 format, UTC+0 timezone.",
        ),
      id: z.string(),
      title: z.string(),
      updatedAt: z
        .string()
        .datetime()
        .transform((date) => new Date(date))
        .describe(
          "The date when the memo was last updated. Display in ISO 8601 format, UTC+0 timezone.",
        ),
    })
  • Import of the getMemos handler from the repository layer into the tools registration file.
    import {
      createCategory,
      deleteCategory,
      getCategories,
      getCategory,
      updateCategory,
    } from "../repository/categories"
    import {
Behavior1/5

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

With no annotations, the description carries full burden but only says 'Get all memos'. It does not disclose return size, ordering, or any side effects. Extremely sparse.

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

Conciseness4/5

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

Extremely concise single sentence with no wasted words. However, it could be more informative without losing conciseness.

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?

Output schema exists but description lacks behavioral context like pagination, ordering, or performance implications. Leaves agent guessing about large data handling.

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

Parameters4/5

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

No parameters exist; schema coverage is 100%. Baseline 4 applies as no additional param info needed beyond schema.

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 'Get all memos' clearly states the tool retrieves all memos, distinguishing from getMemo (single) and searchMemos (search). It is specific but lacks any qualifying scope or limitations.

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?

No guidance on when to use this tool versus siblings like searchMemos or getMemo. No hints about filtering or alternatives.

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