Skip to main content
Glama
jagoff

MEMO MCP Server

by jagoff

memo_evidence_pack

Read-onlyIdempotent

Retrieve cited evidence for any question, or explicitly abstain when retrieval coverage is insufficient.

Instructions

Return bounded, cited evidence for a question, or an explicit abstention.

Read-only, no side effects. Every snippet carries a memo:// citation; when retrieval coverage stays under min_coverage the result is an explicit abstention, never a fabricated answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNoMaximum candidate memories to retrieve (clamped to 1-50).
typeNoRestrict evidence to one memory type (e.g. 'decision', 'fact'); None searches every type.
as_ofNoISO date/datetime for time-travel: only memories valid at that moment are considered.
questionYesNatural-language question to collect cited evidence for.
max_charsNoCharacter budget for the packed evidence text.
min_coverageNoMinimum retrieval coverage (0-1) required to answer; below it the pack abstains explicitly.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds valuable behavioral details: citations are memo://, abstention policy based on min_coverage. No contradictions.

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?

Three sentences, no unnecessary words. The key one-liner is front-loaded, making it easy for an AI to quickly grasp the tool's purpose.

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?

Given the complexity (6 parameters, high schema coverage, output schema exists), the description covers the essential behaviors (citations, abstention). Could be slightly more explicit about output format, but output schema likely compensates.

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 coverage is 100% with clear parameter descriptions. The description does not add significant meaning beyond 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?

Clearly states the tool returns bounded, cited evidence for a question or an explicit abstention. This distinguishes it from sibling tools like memo_search or memo_ask which may not provide citations or abstention.

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

Usage Guidelines4/5

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

Provides usage context: use for cited evidence, expects abstention when coverage is low. However, it does not explicitly contrast with alternatives like memo_search or memo_ask, leaving some ambiguity.

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