Skip to main content
Glama

memory_save

Log a principle/SOP/supplier/learning/content idea/vision/spec to the org's memory. It records a close-out when what-we-believe changes. Title states the claim as a sentence.

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": {
      "project_id": "<project_id>",
      "title": "<title>"
    },
    "name": "memory_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOptional subsystem tag for filtering (free-form).
bodyNoLong-form detail. Related rows are referenced inline (their task IDs) — refs live in the body, not a separate field.
typeNoKnowledge type. Defaults to learning; custom labels are supported. vision — why the organization exists. philosophy — a belief guiding trade-offs, including why it matters. directive — a rule or instruction, including what it supersedes. decision — a steer from the person who owns the project: their words, what it changes, what it replaces, the work it governs. sop — how to carry out a recurring job. spec — what to build and its acceptance criteria. roadmap — direction and outcomes for work ahead. epic — a larger outcome grouping related tasks. task — a concrete piece of current work. bug — behavior that needs correction. report — an observation, incident or customer finding. principle — a reusable rule for making decisions. learning — a lesson supported by experience or evidence. supplier — facts about an external service or supplier. content — a draft or plan for published material. policy — a standing rule governing operations. stance — a position on a subject and its reasoning. When the person who owns the project changes direction, parks or picks something, or overrules a plan, record it as a decision the same day, quoting them.
titleYesThe claim, stated as a sentence. Required, non-empty.
labelsNoOptional tags for filtering.
project_idYesThe org-memory project (UUID, subdomain, slug, or 'default'). Resolved server-side.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish this is a write (readOnlyHint=false), non-destructive, and non-idempotent. The description adds the semantic that an entry captures a belief change, but it never warns that repeated calls create duplicate records — the single most important consequence of idempotentHint=false — nor whether the call returns an identifier an agent would need for later references.

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?

Two tight sentences with no filler, and the purpose is front-loaded before the timing note. Minor awkwardness in the run-on type list ("content idea") costs a point but does not impede parsing.

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 six-parameter write tool with full schema coverage and annotations, the description is adequate but leaves gaps an agent would care about: duplicate behavior given non-idempotency, and what comes back from a call when no output schema exists. The essential purpose is covered, so it is not deficient, just thin.

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 every parameter is already documented, including a long type taxonomy and the inline-reference convention for body. The description's one parameter claim, "Title states the claim as a sentence," merely restates the schema's own text, adding no new meaning. Baseline 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?

"Log ... to the org's memory" gives a specific verb and destination, and the list of knowledge types (principle/SOP/supplier/learning/vision/spec) narrows the scope meaningfully. It stops short of distinguishing itself from the sibling memory_search (retrieval vs. write), so an agent must infer that contrast from the verb alone.

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?

"It records a close-out when what-we-believe changes" implies a timing condition (record when beliefs/direction change), which is real guidance. There is no explicit when-not, no mention of preferring memory_search first to avoid duplicates, and no statement of what to do if a similar entry already exists.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources