Skip to main content
Glama
Sign In
engram-mcp

engram-mcp

by Cartisien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

recall_user

Retrieve memories associated with a specific user, optionally filtered by a search query and limited results. Accessible from any session context.

Instructions

Recall user-scoped memories — works from any session context.

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": {
      "userId": "<userId>"
    },
    "name": "recall_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesUser identifier
queryNoSearch query (optional — returns all if omitted)
limitNoMax results (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the functional scope and session context, omitting read-only nature, side effects, permissions, or error behavior. This is insufficient for a read operation.

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 description is a single, efficient sentence covering the core purpose and context. It is front-loaded and contains no unnecessary words, though it could incorporate more detail without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description is too brief. It does not explain return format, pagination, or error handling, and lacks contrast with siblings like 'recall' or 'recall_recent' beyond the user-scoped hint.

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?

All parameters have descriptions in the schema (100% coverage), so baseline is 3. The description does not add meaning beyond the schema; it reinforces 'user-scoped' which aligns with userId but adds no extra semantic value.

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 clearly states the verb 'recall' and resource 'user-scoped memories', distinguishing it from siblings like 'recall' and 'recall_by_time'. The phrase 'works from any session context' adds clarity about availability.

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?

The mention of 'user-scoped' and 'any session context' gives implied usage guidance but does not explicitly state when to use this tool versus alternatives like 'recall' or 'recall_recent'. No when-not-to-use or exclusion criteria are provided.

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