Skip to main content
Glama
jagoff

MEMO MCP Server

by jagoff
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

memo_federation_preview

Read-onlyIdempotent

Preview the exact memories a recipient's access permissions would include in a signed bundle, using the recipient's device ID to filter by ACL visibility.

Instructions

Preview the exact memories an ACL would allow into a signed bundle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
principalYesPrincipal (device id) of the intended bundle recipient whose ACL-visible memories are previewed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed1 schema field changedv4.4.6
    • addedInput schema / properties / principal / description
      Added value: +"Principal (device id) of the intended bundle recipient whose ACL-visible memories are previewed."
  2. Addedv4.4.4

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate a safe, read-only, idempotent operation. The description adds context about ACL authorization and signed bundles, enhancing understanding of the tool's behavior without contradicting annotations.

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, concise sentence that immediately conveys the tool's purpose with no unnecessary words.

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

Completeness4/5

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

Combined with the input schema and annotations, the description provides sufficient context. The output schema further aids completeness. Minor clarification linking the principal to the ACL would improve it.

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 describes the 'principal' parameter thoroughly. The tool description does not add extra meaning beyond the schema, so parameter semantics are adequately covered.

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?

The description clearly states the tool's purpose: to preview which memories an ACL would allow into a signed bundle. The verb 'Preview' and specific resource 'exact memories' make it distinct from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used for previewing memories under ACL constraints, but it provides no explicit guidance on when to use this tool over others or when not to use it.

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