Skip to main content
Glama
Sign In
Memorable MCP Server

Memorable MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

memorable_generate_embedding

Generate or refresh a memory's 1024-dimensional vector embedding with Ollama, either synchronously or as a background job.

Instructions

Generate or refresh the 1024-dimensional vector embedding for a memory using Ollama (synchronous or async background job)

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_generate_embedding"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the memory to vectorize
asyncNoWhether to enqueue embedding generation as a background job (default false = synchronous)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 it does disclose useful traits: a fixed 1024-dimension output, the Ollama backend, and the synchronous vs. background-job execution mode. However, it omits whether the call overwrites an existing embedding, whether the memory must already exist, error/retry behavior, and what is returned.

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?

A single compact sentence that front-loads the action and resource, then adds only the two pieces of context an agent actually needs (dimension/provider, execution mode). No filler or repetition.

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 two-parameter, no-annotation, no-output-schema tool, the description covers the action and the execution-mode tradeoff but leaves key operational facts unstated: return value, whether an existing vector is replaced, and preconditions on the memory id.

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%, so both parameters are already documented in the schema; the description's mention of 'synchronous or async background job' largely restates the async parameter's schema text. The word 'refresh' hints at idempotent recomputation but no additional meaning is contributed.

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?

Specific verb ('Generate or refresh') plus a precise resource ('the 1024-dimensional vector embedding for a memory') and the backing provider (Ollama). No sibling in the list performs embedding work, so the purpose is unambiguous, though the description never states that distinction explicitly.

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?

It says nothing about when an agent should call this versus alternatives such as memorable_search or memorable_find_neighbors, nor whether embeddings must exist before those tools work or must be refreshed after memorable_update_memory. The async option is named but no condition for choosing it is given.

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