Skip to main content
Glama

Recall from RAMen Memory

recall
Read-onlyIdempotent

Fetches the user's saved context from earlier chats across AI apps—family, work, projects, rules, preferences and plans—so assistants can answer questions that depend on who the user is.

Instructions

Look up what the user told you or their other AI apps in earlier chats: their family, work, projects, rules, preferences and plans, kept in their RAMen Memory. Use it when a conversation starts on something that depends on who the user is, and when they refer to something that is not in this chat. It always gives the user's must-know facts too; for how to answer (style, length, tone), their profile card first.

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": {
      "question": "<question>"
    },
    "name": "recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYeswhat you need to know, in the user's words, for example 'What is my wholesale pricing rule?'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the baseline burden is low. The description adds real behavioral context beyond them: it discloses that results 'always give the user's must-know facts too,' which tells the agent to expect unsolicited supplementary content in the response — useful since there is no output schema.

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?

The verb and resource are front-loaded in the first clause, and every sentence carries routing or behavioral information. The first sentence is long and stacks a colon list plus an app reference, and the trailing 'profile card' clause is slightly dangling, but there is no filler.

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 single-parameter, read-only lookup with no output schema, the description covers what is retrieved, when to call it, and that must-know facts are always included. The one loose end is the unexplained reference to 'their profile card,' which leaves the agent unsure whether that is a sibling tool or a stored artifact.

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?

There is a single parameter with 100% schema description coverage, including an example phrasing ('What is my wholesale pricing rule?'), so the schema already does the heavy lifting. The description reinforces the domain of acceptable questions via the family/work/projects list but adds no syntax, formatting, or phrasing guidance beyond what the schema states.

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 gives a specific verb and resource — 'Look up what the user told you ... in earlier chats' — and enumerates the content domain (family, work, projects, rules, preferences, plans) stored in RAMen Memory. It partially distinguishes itself from siblings by routing style/tone questions to the 'profile card' instead, though it never names that tool, so an agent must infer which sibling that is.

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?

It states concrete triggering conditions: 'when a conversation starts on something that depends on who the user is' and 'when they refer to something that is not in this chat.' It also names an alternative destination for style/length/tone questions. It stops short of an explicit exclusion (e.g., 'do not use for X' or naming forget/remember/recall_thread as alternatives), which keeps it below a 5.

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