Skip to main content
Glama
RyoJerryYu

MCP Server Memos

by RyoJerryYu

create_memo

Create a memo by providing content and optionally setting its visibility. This tool adds new memos to your Memos server.

Instructions

Create a new memo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe content of the memo.
visibilityNoThe visibility of the memo.PRIVATE

Implementation Reference

  • The create_memo async method on MemoServiceToolAdapter that handles the tool execution logic. It validates input args using CreateMemoRequest schema, constructs a proto CreateMemoRequest, calls the gRPC memo_service.create_memo, and returns a text response.
    async def create_memo(self, args: dict) -> list[types.TextContent]:
        try:
            params = CreateMemoRequest.model_validate(args)
        except Exception as e:
            raise McpError(types.INVALID_PARAMS, str(e))
    
        req = memos_api_v1.CreateMemoRequest(
            content=params.content,
            visibility=params.visibility.to_proto(),
        )
        res = await self.memo_service.create_memo(create_memo_request=req)
        content = f"Memo created: {res.name}"
        return [types.TextContent(type="text", text=content)]
  • CreateMemoRequest Pydantic model defining the tool's input schema: content (required string) and visibility (optional, defaults to PRIVATE).
    class CreateMemoRequest(BaseModel):
        """Request to create memo"""
    
        content: Annotated[
            str,
            Field(
                description="""The content of the memo.""",
            ),
        ]
        visibility: Annotated[
            Visibility,
            Field(default=Visibility.PRIVATE, description="""The visibility of the memo."""),
        ]
  • Registration of create_memo tool in list_tools: name=MemosTools.CREATE_MEMO ('create_memo'), description 'Create a new memo', inputSchema from CreateMemoRequest.
    types.Tool(
        name=MemosTools.CREATE_MEMO,
        description="Create a new memo",
        inputSchema=CreateMemoRequest.model_json_schema(),
    ),
  • Routing of 'create_memo' tool call in call_tool handler to tool_adapter.create_memo(args).
    elif name == MemosTools.CREATE_MEMO:
        return await tool_adapter.create_memo(args)
  • MemosTools enum defining CREATE_MEMO = 'create_memo' constant used for tool name registration and routing.
    class MemosTools(str, Enum):
        LIST_MEMO_TAGS = "list_memo_tags"
        SEARCH_MEMO = "search_memo"
        CREATE_MEMO = "create_memo"
        GET_MEMO = "get_memo"
Behavior2/5

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

With no annotations, the description carries full burden for behavioral transparency. It only says 'Create a new memo', omitting side effects, permissions, idempotency, or any other behavioral traits. This is insufficient.

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

Conciseness3/5

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

The description is very concise (one sentence), but it is under-specified. Conciseness is not automatically high; it should balance brevity with informativeness. Here, it is acceptable but not exceptional.

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?

The description lacks details about return values, side effects, or post-creation behavior. Given no output schema, the description should compensate, but it does not. Incomplete for a creation tool.

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?

Input schema coverage is 100% with descriptions for both parameters (content and visibility). The tool description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.

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 action (create) and resource (memo), making the purpose obvious. However, it does not differentiate from siblings like get_memo or search_memo, but those are distinct operations, so clarity is high.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it, which is a significant gap.

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/RyoJerryYu/mcp-server-memos-py'

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