Skip to main content
Glama
RyoJerryYu

MCP Server Memos

by RyoJerryYu

get_memo

Retrieve specific memos from the MCP Server Memos by providing the memo name, enabling quick access to stored information.

Instructions

Get a memo

Input Schema

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

Implementation Reference

  • The main handler function for the 'get_memo' tool. It validates the input arguments using GetMemoRequest schema, constructs a gRPC request to fetch the memo by name from the memo_service stub, formats the response content, and returns it as MCP TextContent.
    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 BaseModel defining the input schema for the get_memo tool, which requires a single 'name' field (format: memos/{id}). Used for validation in the handler and as inputSchema in tool registration.
    class GetMemoRequest(BaseModel):
        """Request to get memo"""
    
        name: Annotated[
            str,
            Field(
                description="""The name of the memo.
    Format: memos/{id}
    """
            ),
        ]
  • Tool registration in the MCP server's list_tools() decorator. Defines the tool name 'get_memo', description, and input schema.
    types.Tool(
        name=MemosTools.GET_MEMO,
        description="Get a memo",
        inputSchema=GetMemoRequest.model_json_schema(),
    ),
  • Dispatch logic in the MCP server's call_tool() decorator that routes calls to the get_memo handler when the tool name matches.
    elif name == MemosTools.GET_MEMO:
        return await tool_adapter.get_memo(args)
  • Enum value in MemosTools defining the string constant for the 'get_memo' tool name, used throughout for comparisons and registration.
    GET_MEMO = "get_memo"
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 but fails to do so. 'Get a memo' implies a read-only operation, but it doesn't specify whether this requires authentication, what happens if the memo doesn't exist, if there are rate limits, or what format the memo is returned in. The description lacks critical behavioral context needed for safe and effective invocation.

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?

While concise with only three words, the description is under-specified rather than efficiently structured. It doesn't front-load key information (e.g., 'Retrieve a single memo by its identifier') and wastes its brevity on a tautology. Every sentence should earn its place, but here the single phrase adds minimal value beyond the tool name.

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 simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It doesn't explain what 'get' entails (e.g., returns memo content or metadata), how errors are handled, or basic usage context. For a tool with no output schema, the description should at least hint at the return type, but it provides no such information.

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 schema description coverage is 100%, with the parameter 'name' documented as 'The name of the memo. Format: memos/{id}'. The description adds no additional meaning beyond what the schema provides, such as explaining the ID format further or usage examples. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 'Get a memo' is a tautology that essentially restates the tool name without providing meaningful specificity. It doesn't distinguish this tool from its siblings (create_memo, list_memo_tags, search_memo) or clarify what 'get' means in this context (retrieve by ID, fetch content, etc.). While the verb 'get' is clear, the description lacks the specificity needed for effective tool selection.

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 that this tool retrieves a single memo by its identifier (as implied by the parameter), nor does it contrast with siblings like search_memo (which likely searches across memos) or list_memo_tags (which handles tags). There's no context about prerequisites, exclusions, or appropriate use cases.

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