Skip to main content
Glama
jagoff

MEMO MCP Server

by jagoff
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

memo_profile

Read-onlyIdempotent

Retrieves bounded stable and active memory with evidence metadata, giving you relevant project and user context to recall past decisions and information.

Instructions

Return bounded stable and active memory with evidence metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory used to resolve the current project (git toplevel) so the project-specific profile document is included in the stable section. Defaults to the server process's working directory.
limitNoMaximum recent memory records in the 'active' section (clamped to 0-50; forgotten records are excluded).
scopeNoDescriptive label echoed into the payload: one of 'current', 'user', 'project', 'agent' (anything else returns a memo.error.v1 invalid_scope envelope). Does not filter or authorize — content selection stays governed by Memo's profile files and record provenance.current
sourceNoCaller identity recorded in the recall consult log. Empty string falls back to the MEMO_SOURCE env var, then the MCP client's declared clientInfo name.
budget_charsNoCharacter budget for the 'stable' profile text (clamped to 256-12000). Longer text is truncated with a trailing ellipsis and an entry in 'omissions'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv4.4.6
    • addedInput schema / properties / budget_chars / description
      Added value: +"Character budget for the 'stable' profile text (clamped to 256-12000). Longer text is truncated with a trailing ellipsis and an entry in 'omissions'."
    • addedInput schema / properties / cwd / description
      Added value: +"Working directory used to resolve the current project (git toplevel) so the project-specific profile document is included in the stable section. Defaults to the server process's working directory."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum recent memory records in the 'active' section (clamped to 0-50; forgotten records are excluded)."
    • addedInput schema / properties / scope / description
      Added value: +"Descriptive label echoed into the payload: one of 'current', 'user', 'project', 'agent' (anything else returns a memo.error.v1 invalid_scope envelope). Does not filter or authorize — content selection stays governed by Memo's profile files and record provenance."
    • addedInput schema / properties / source / description
      Added value: +"Caller identity recorded in the recall consult log. Empty string falls back to the MEMO_SOURCE env var, then the MCP client's declared clientInfo name."
  2. Addedv4.4.4

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds that results are bounded by budget_chars and include stable/active sections with evidence metadata, providing useful behavioral nuance beyond annotations.

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?

Description is a single sentence that conveys the core function efficiently. However, it uses jargon ('bounded stable and active memory') that may require prior context; a slightly more structured breakdown could improve clarity.

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 presence of an output schema and detailed parameter descriptions, the description is mostly complete. However, it does not explain what 'stable' vs 'active' memory means or how evidence metadata is structured, which could be ambiguous for an agent.

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 100%; each parameter is well-documented in the schema. The description does not add additional meaning beyond what is already in the schema, so a baseline score of 3 is appropriate.

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

Purpose5/5

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

Description clearly states it returns bounded stable and active memory with evidence metadata. This is specific to the tool's function and distinguishes it from siblings like memo_search (search) and memo_context (context retrieval).

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 alternatives such as memo_context or memo_unified_briefing. No indication of prerequisites or exclusions.

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/jagoff/memo'

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