Skip to main content
Glama
108yen
by 108yen

Search Memos

searchMemos

Search memos by keyword and date range to quickly find specific notes stored in the memo-mcp server database.

Instructions

Search memos by keyword and date range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryIdNo
endNoEnd date for the search range use ISO 8601 format. ex: 2020-02-01T00:00:00+09:00
queryNo
startNoStart date for the search range use ISO 8601 format. ex: 2020-01-01T00:00:00+09:00

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
memosYes

Implementation Reference

  • Core handler function that performs the memo search by filtering based on query, categoryId, and date range (start/end). Reads from DB and returns matching memos.
    export const searchMemos = async (params: SearchMemosParams) => {
      const { categoryId, end, query, start } = params
      await db.read()
    
      return db.data.memos.filter((memo) => {
        if (query && !memo.content.includes(query) && !memo.title.includes(query)) {
          return false
        }
    
        if (categoryId && memo.categoryId !== categoryId) {
          return false
        }
    
        const updatedAt = new Date(memo.updatedAt).getTime()
    
        if (start && updatedAt < start.getTime()) {
          return false
        }
        if (end && updatedAt > end.getTime()) {
          return false
        }
        return true
      })
    }
  • Zod schema defining input parameters for searchMemos: optional categoryId, query, start/end dates with datetime parsing.
    export const SearchMemosSchema = z.object({
      categoryId: z.string().optional(),
      end: z
        .string()
        .datetime({
          message: "Invalid date format. Please use ISO 8601 format.",
          offset: true,
        })
        .transform((date) => new Date(date))
        .optional()
        .describe(
          "End date for the search range use ISO 8601 format. ex: 2020-02-01T00:00:00+09:00",
        ),
      query: z.string().optional(),
      start: z
        .string()
        .datetime({
          message: "Invalid date format. Please use ISO 8601 format.",
          offset: true,
        })
        .transform((date) => new Date(date))
        .optional()
        .describe(
          "Start date for the search range use ISO 8601 format. ex: 2020-01-01T00:00:00+09:00",
        ),
    })
    
    export type SearchMemosParams = z.infer<typeof SearchMemosSchema>
  • Registers the searchMemos tool with the MCP server, specifying input/output schemas, description, and a thin handler that delegates to the repository function and formats the response.
    server.registerTool(
      "searchMemos",
      {
        description: "Search memos by keyword and date range",
        inputSchema: SearchMemosSchema.shape,
        outputSchema: { memos: z.array(MemoSchema) },
        title: "Search Memos",
      },
      async (params) => {
        const memos = await searchMemos(params)
        return {
          content: [{ text: JSON.stringify(memos), type: "text" }],
          structuredContent: { memos },
        }
      },
    )
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the search action but doesn't describe whether it's read-only, if it requires authentication, what the output looks like (though an output schema exists), or any rate limits. This leaves significant gaps for a tool with 4 parameters.

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 a single, efficient sentence with zero waste, front-loading the key information. Every word earns its place, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (4 parameters, no annotations, but with an output schema), the description is minimally adequate. It covers the basic purpose but lacks usage guidelines and behavioral details, relying on the output schema for return values. This leaves room for improvement in completeness.

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?

Schema description coverage is 50% (2 of 4 parameters have descriptions: 'start' and 'end'), and the description mentions 'keyword and date range', which partially maps to 'query', 'start', and 'end'. However, it doesn't explain 'categoryId' or add details beyond the schema, resulting in marginal value over the structured data.

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 clearly states the verb ('Search') and resource ('memos'), specifying the search criteria ('by keyword and date range'). It distinguishes from siblings like 'getMemos' by indicating a filtered search rather than a simple retrieval, though it doesn't explicitly contrast with all siblings.

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 like 'getMemos' or 'getMemo', nor does it mention prerequisites or exclusions. It implies usage for searching with specific criteria but lacks explicit context for selection among sibling tools.

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