Skip to main content
Glama
RyoJerryYu

MCP Server Memos

by RyoJerryYu

get_memo

Retrieve a specific memo by its name to view its content.

Instructions

Get a memo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the memo. Format: memos/{id}

Implementation Reference

  • The handler method `get_memo` on MemoServiceToolAdapter that validates input via GetMemoRequest, calls the gRPC MemoService.get_memo, and returns the memo content.
    async def get_memo(self, args: dict) -> list[types.TextContent]:
        try:
            params = GetMemoRequest.model_validate(args)
        except Exception as e:
            raise McpError(types.INVALID_PARAMS, str(e))
    
        req = memos_api_v1.GetMemoRequest(name=params.name)
        res = await self.memo_service.get_memo(get_memo_request=req)
        content = f"Memo:\n{res.content}"
        return [types.TextContent(type="text", text=content)]
  • Pydantic schema for GetMemoRequest with a required 'name' field (format: memos/{id}).
    class GetMemoRequest(BaseModel):
        """Request to get memo"""
    
        name: Annotated[
            str,
            Field(
                description="""The name of the memo.
    Format: memos/{id}
    """
            ),
        ]
  • Registration of the get_memo tool in the list_tools() with its name, description, and input schema.
    types.Tool(
        name=MemosTools.GET_MEMO,
        description="Get a memo",
        inputSchema=GetMemoRequest.model_json_schema(),
    ),
  • Dispatch in call_tool() that routes the 'get_memo' tool name to the handler method.
    elif name == MemosTools.GET_MEMO:
        return await tool_adapter.get_memo(args)
  • Enum constant MemosTools.GET_MEMO defining the string 'get_memo' used for registration and dispatch.
    GET_MEMO = "get_memo"
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It only states 'Get' which implies a read, but it does not mention idempotency, side effects, authentication needs, or any constraints.

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

Conciseness2/5

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

The description is extremely concise at three words, but it sacrifices necessary detail. It fails to add value beyond the tool name, making it under-specified rather than efficiently concise.

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 no output schema and no annotations, the description should compensate by explaining what the memo contains or the return format. It does not, leaving the agent underinformed for a simple get operation.

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 input schema already provides a clear description for the 'name' parameter (format: memos/{id}), so the description adds no new meaning. With 100% schema coverage, a baseline of 3 is appropriate.

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

Purpose3/5

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

The description 'Get a memo' clearly states the action and resource, but it is too vague to distinguish from sibling tools like 'search_memo'. It lacks specificity about what kind of memo or scope.

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 usage guidance is provided. The description does not indicate when to use 'get_memo' versus alternatives like 'create_memo' or 'search_memo'.

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