Skip to main content
Glama
Sign In
Memorable MCP Server

Memorable MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

memorable_create_memory

Create a new persistent memory with a title and Markdown body; automatically enqueues a vector embedding for semantic retrieval.

Instructions

Create a new memory in Memorable (automatically enqueues vector embedding in the background)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "memorable_create_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoMarkdown content, instructions, or knowledge context
titleYesTitle or headline of the memory
pinnedNoWhether this memory should be pinned to the top of the workspace
pinned_positionNoOptional manual order index for pinned memory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and its one substantive disclosure — that a vector embedding is automatically enqueued in the background — is genuinely non-obvious and useful. However, it omits whether the embedding is synchronous or eventual from the caller's perspective, what is returned, and whether any permissions or workspace scoping apply.

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?

A single front-loaded sentence with the key side effect in parentheses; nothing is wasted. It is arguably too terse given the lack of usage guidance, but the prose itself is clean.

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?

For a 4-parameter mutation tool with no annotations and no output schema, the description covers the core action and the background embedding side effect but leaves the return value and preconditions unstated. It is adequate-but-thin rather than complete.

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%, so all four parameters (title, body, pinned, pinned_position) are already documented in the schema, and the description adds no extra semantics such as markdown expectations or pin ordering rules. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose4/5

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

"Create a new memory in Memorable" states a specific verb and resource that clearly separates it from update, append, or delete siblings. It stops short of naming how it differs from memorable_append_to_memory, but the intent is unambiguous.

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 versus memorable_append_to_memory, memorable_update_memory, or memorable_create-with-attachment flows. The agent must infer from sibling names alone that create is for new memories rather than extending existing ones.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools