Skip to main content
Glama
Sign In
Memorable MCP Server

Memorable MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

memorable_get_memory

Retrieve a memory's full Markdown content, embedding status, attachments, and optional rendered HTML by its unique ID for recall or reuse.

Instructions

Retrieve a memory's full Markdown content, embedding status, attachments, and optional rendered HTML

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": {
      "id": "<id>"
    },
    "name": "memorable_get_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the memory
render_markdownNoWhether to include rendered HTML for the memory Markdown body

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?

No annotations are supplied, so the description carries the full burden. It does useful work by disclosing the return payload (Markdown body, embedding status, attachments, optional HTML), which is valuable with no output schema, but it says nothing about read-only semantics, behavior when the id does not exist, or the cost of rendering HTML.

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 no filler; the return payload is listed immediately after the verb and resource. It is slightly clipped as a fragment and could name the id input, but nothing is wasted.

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?

For a two-parameter read tool with no output schema and no annotations, enumerating the returned fields is the main completeness requirement and it is met. Remaining gaps (not-found behavior, guidance versus search/list siblings) are minor for this complexity level.

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 both parameters are already documented in structured form. The description reinforces the render_markdown flag by framing the HTML as 'optional rendered HTML', but adds no format or default detail beyond the schema, so the baseline of 3 applies.

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?

The description pairs a specific verb ('Retrieve') with a specific resource ('a memory's full Markdown content') and enumerates what comes back (embedding status, attachments, optional rendered HTML). That makes it clearly a single-record fetch by id rather than a list or search operation, though it never names the siblings it contrasts with.

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?

There is no when-to-use guidance at all: nothing says to prefer this over memorable_search, memorable_recall_context, or memorable_list_memories when looking for content, and nothing explains when render_markdown is worth enabling. Usage is only inferable from the phrase 'a memory's' plus the required id.

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