XMemo

Build XMemo context

recall_context

Read-onlyIdempotent

Build a read-only, bounded context pack from multiple relevant memories. Use it when an answer needs several memory items or scoped/path-filtered context; use recall for a quick best-effort lookup or get_project_context for a whole-project snapshot. max_items/max_tokens bound output: memories that do not fit are omitted and reported, so raise max_tokens or use recall when you need the records themselves.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Candidate-result limit; 0 derives it from the item/token budgets.
`query`	Yes	Natural-language query used to rank memories for the context pack.
`scope`	No	Optional authorized scope; blank uses the token default.
`since`	No	RFC 3339 timestamp with timezone offset (e.g., '2026-09-01T00:00:00+09:00'). Trigger: Call this whenever the user query mentions any relative or absolute time constraint in any language (e.g., today, yesterday, last week, last month, recently, Aug 1, Aug 10 to Sep 1, since Monday, before Sep 15, in Q3). Model responsibility: You (the calling LLM) know current date and user local time, so you must convert natural language time expressions into absolute timestamps. Consequence: If omitted, the server falls back to heuristic guessing which may misinterpret timezone day boundaries or relative dates.
`until`	No	RFC 3339 timestamp with timezone offset (e.g., '2026-09-02T00:00:00+09:00'). When used with since, defines the half-open interval [since, until) with until > since (maximum 90 days span). Trigger: Pass when the user query specifies an end date or bounded window in any language (e.g., yesterday end of day, by Aug 10, Aug 10 to Sep 1). Model responsibility: Convert natural language end bounds into absolute timestamps with timezone offsets. Consequence: If omitted, the window is open-ended on the upper side or derived heuristically.
`bucket`	No	Accessible bucket filter; % includes all accessible buckets.	%
`team_id`	No	Optional exact authorized team filter.
`agent_id`	No	Optional client-supplied agent label for memory attribution.
`max_items`	No	Maximum memories rendered in the context pack.
`max_tokens`	No	Approximate token budget for the rendered context pack.
`query_mode`	No	Optional query intent: 'topic' (default) or 'activity_log'. Trigger: Set 'activity_log' for event feeds within a bounded [since, until) window; set 'topic' for topic retrieval. Model responsibility: 'activity_log' requires explicit bounded 'since' and 'until' timestamps. Consequence: 'activity_log' without bounds fails closed; explicit 'topic' blocks stream bypass.
`time_order`	No	Sort order for returned memories: 'desc' (newest first) or 'asc' (oldest first). Trigger: Pass 'desc' when the user asks for 'latest', 'recent', 'newest first', or recency, or 'asc' for chronological order ('oldest first') in any language. Model responsibility: Explicitly set desired temporal ordering when the user expresses recency intent. If omitted and since/until are omitted, default relevance ranking is used without temporal sorting.
`memory_type`	No	Memory type filter; auto searches the normal mixed set.	auto
`output_json`	No	True returns the full structured pack; false returns rendered context text.
`path_filter`	No	Case-insensitive memory-path pattern; % matches all paths.	%
`owner_timezone`	No	The user's real IANA timezone, such as Asia/Tokyo or America/Los_Angeles. Required for honest calendar periods; never guess UTC.
`prefer_working`	No	True prioritizes active working/session-state signals.
`reference_time`	No	Optional ISO 8601 reference time snapshot for deterministic evaluation. Leave blank to use the real clock; setting this does not replace owner_timezone for calendar day boundaries.
`agent_instance_id`	No	Optional stable, non-secret agent instance ID for per-client attribution.
`temporal_axis_mode`	No	Optional temporal axis resolution policy: 'created_at' (Scheme A), 'updated_at' (Scheme B), or 'split_filter_created_order_updated' (Scheme C).
`hypothetical_answer`	No	Optional multilingual hypothetical answer or dense semantic expansion written by the calling LLM for this query.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedSep 11, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / agent_id

Added value: +{
+  "default": "",
+  "description": "Optional client-supplied agent label for memory attribution.",
+  "type": "string"
+}

addedInput schema / properties / agent_instance_id

Added value: +{
+  "default": "",
+  "description": "Optional stable, non-secret agent instance ID for per-client attribution.",
+  "type": "string"
+}

addedInput schema / properties / bucket

Added value: +{
+  "default": "%",
+  "description": "Accessible bucket filter; % includes all accessible buckets.",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 0,
+  "description": "Candidate-result limit; 0 derives it from the item/token budgets.",
+  "type": "integer"
+}

addedInput schema / properties / memory_type

Added value: +{
+  "default": "auto",
+  "description": "Memory type filter; auto searches the normal mixed set.",
+  "type": "string"
+}

addedInput schema / properties / output_json

Added value: +{
+  "default": false,
+  "description": "True returns the full structured pack; false returns rendered context text.",
+  "type": "boolean"
+}

addedInput schema / properties / owner_timezone

Added value: +{
+  "default": "",
+  "description": "The user's real IANA timezone, such as Asia/Tokyo or America/Los_Angeles. Required for honest calendar periods; never guess UTC.",
+  "type": "string"
+}

addedInput schema / properties / path_filter

Added value: +{
+  "default": "%",
+  "description": "Case-insensitive memory-path pattern; % matches all paths.",
+  "type": "string"
+}

addedInput schema / properties / prefer_working

Added value: +{
+  "default": true,
+  "description": "True prioritizes active working/session-state signals.",
+  "type": "boolean"
+}

addedInput schema / properties / reference_time

Added value: +{
+  "default": "",
+  "description": "Optional ISO 8601 reference time snapshot for deterministic evaluation. Leave blank to use the real clock; setting this does not replace owner_timezone for calendar day boundaries.",
+  "type": "string"
+}

addedInput schema / properties / scope

Added value: +{
+  "default": "",
+  "description": "Optional authorized scope; blank uses the token default.",
+  "type": "string"
+}

addedInput schema / properties / team_id

Added value: +{
+  "default": "",
+  "description": "Optional exact authorized team filter.",
+  "type": "string"
+}

addedInput schema / properties / temporal_axis_mode

Added value: +{
+  "default": "",
+  "description": "Optional temporal axis resolution policy: 'created_at' (Scheme A), 'updated_at' (Scheme B), or 'split_filter_created_order_updated' (Scheme C).",
+  "type": "string"
+}

Changed3 schema fields changedSep 7, 2026

changedInput schema / properties / since / description

Previous value: -"RFC 3339 timestamp with timezone offset (e.g., '2026-09-01T00:00:00+09:00'). Trigger: Call this whenever the user query mentions any relative or absolute time constraint (今天/今日/昨天/昨日/前天/上周/8月1日/8月10日到9月1日/最近...). Model responsibility: You (the calling LLM) know current date and user local time, so you must convert natural language time expressions into absolute timestamps. Consequence: If omitted, the server falls back to heuristic guessing which may misinterpret timezone day boundaries or relative dates."New value: +"RFC 3339 timestamp with timezone offset (e.g., '2026-09-01T00:00:00+09:00'). Trigger: Call this whenever the user query mentions any relative or absolute time constraint in any language (e.g., today, yesterday, last week, last month, recently, Aug 1, Aug 10 to Sep 1, since Monday, before Sep 15, in Q3). Model responsibility: You (the calling LLM) know current date and user local time, so you must convert natural language time expressions into absolute timestamps. Consequence: If omitted, the server falls back to heuristic guessing which may misinterpret timezone day boundaries or relative dates."

changedInput schema / properties / time_order / description

Previous value: -"Sort order for returned memories: 'desc' (newest first) or 'asc' (oldest first). Trigger: Pass 'desc' when the user asks for 'latest', 'recent', '从新到旧', or timeline recency, or 'asc' for chronological order. Model responsibility: Explicitly set desired temporal ordering when the user expresses recency intent. If omitted and since/until are omitted, default relevance ranking is used without temporal sorting."New value: +"Sort order for returned memories: 'desc' (newest first) or 'asc' (oldest first). Trigger: Pass 'desc' when the user asks for 'latest', 'recent', 'newest first', or recency, or 'asc' for chronological order ('oldest first') in any language. Model responsibility: Explicitly set desired temporal ordering when the user expresses recency intent. If omitted and since/until are omitted, default relevance ranking is used without temporal sorting."

changedInput schema / properties / until / description

Previous value: -"RFC 3339 timestamp with timezone offset (e.g., '2026-09-02T00:00:00+09:00'). When used with since, defines the half-open interval [since, until) with until > since (maximum 90 days span). Trigger: Pass when the user query specifies an end date or bounded window (e.g., 昨天 end of day, 截至8月10日, 8月10日到9月1日). Model responsibility: Convert natural language end bounds into absolute timestamps with timezone offsets. Consequence: If omitted, the window is open-ended on the upper side or derived heuristically."New value: +"RFC 3339 timestamp with timezone offset (e.g., '2026-09-02T00:00:00+09:00'). When used with since, defines the half-open interval [since, until) with until > since (maximum 90 days span). Trigger: Pass when the user query specifies an end date or bounded window in any language (e.g., yesterday end of day, by Aug 10, Aug 10 to Sep 1). Model responsibility: Convert natural language end bounds into absolute timestamps with timezone offsets. Consequence: If omitted, the window is open-ended on the upper side or derived heuristically."

Changed5 schema fields changedSep 5, 2026

addedInput schema / properties / hypothetical_answer

Added value: +{
+  "default": "",
+  "description": "Optional multilingual hypothetical answer or dense semantic expansion written by the calling LLM for this query.",
+  "type": "string"
+}

addedInput schema / properties / query_mode

Added value: +{
+  "default": "",
+  "description": "Optional query intent: 'topic' (default) or 'activity_log'. Trigger: Set 'activity_log' for event feeds within a bounded [since, until) window; set 'topic' for topic retrieval. Model responsibility: 'activity_log' requires explicit bounded 'since' and 'until' timestamps. Consequence: 'activity_log' without bounds fails closed; explicit 'topic' blocks stream bypass.",
+  "type": "string"
+}

addedInput schema / properties / since

Added value: +{
+  "default": "",
+  "description": "RFC 3339 timestamp with timezone offset (e.g., '2026-09-01T00:00:00+09:00'). Trigger: Call this whenever the user query mentions any relative or absolute time constraint (今天/今日/昨天/昨日/前天/上周/8月1日/8月10日到9月1日/最近...). Model responsibility: You (the calling LLM) know current date and user local time, so you must convert natural language time expressions into absolute timestamps. Consequence: If omitted, the server falls back to heuristic guessing which may misinterpret timezone day boundaries or relative dates.",
+  "type": "string"
+}

addedInput schema / properties / time_order

Added value: +{
+  "default": "",
+  "description": "Sort order for returned memories: 'desc' (newest first) or 'asc' (oldest first). Trigger: Pass 'desc' when the user asks for 'latest', 'recent', '从新到旧', or timeline recency, or 'asc' for chronological order. Model responsibility: Explicitly set desired temporal ordering when the user expresses recency intent. If omitted and since/until are omitted, default relevance ranking is used without temporal sorting.",
+  "type": "string"
+}

addedInput schema / properties / until

Added value: +{
+  "default": "",
+  "description": "RFC 3339 timestamp with timezone offset (e.g., '2026-09-02T00:00:00+09:00'). When used with since, defines the half-open interval [since, until) with until > since (maximum 90 days span). Trigger: Pass when the user query specifies an end date or bounded window (e.g., 昨天 end of day, 截至8月10日, 8月10日到9月1日). Model responsibility: Convert natural language end bounds into absolute timestamps with timezone offsets. Consequence: If omitted, the window is open-ended on the upper side or derived heuristically.",
+  "type": "string"
+}

Changed1 schema field changedSep 5, 2026
- changedInput schema / properties / max_tokens / default
```
Previous value: -1500New value: +8000
```
Changed1 schema field changedSep 5, 2026
- changedInput schema / properties / max_tokens / default
```
Previous value: -8000New value: +1500
```
Changed1 schema field changedSep 1, 2026
- changedInput schema / properties / max_tokens / default
```
Previous value: -1500New value: +8000
```

Changed20 schema fields changedJul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / agent_id

Removed value: -{
-  "default": "",
-  "description": "Optional client-supplied agent label for memory attribution.",
-  "title": "Agent Id",
-  "type": "string"
-}

removedInput schema / properties / agent_instance_id

Removed value: -{
-  "default": "",
-  "description": "Optional stable, non-secret agent instance ID for per-client attribution.",
-  "title": "Agent Instance Id",
-  "type": "string"
-}

removedInput schema / properties / bucket

Removed value: -{
-  "default": "%",
-  "description": "Memory bucket or namespace to read from or write to; use % only for tools that support wildcard reads.",
-  "title": "Bucket",
-  "type": "string"
-}

removedInput schema / properties / limit

Removed value: -{
-  "default": 0,
-  "description": "Maximum number of results to return.",
-  "title": "Limit",
-  "type": "integer"
-}

changedInput schema / properties / max_items / description

Previous value: -"Maximum number of memory items to include."New value: +"Maximum memories rendered in the context pack."

removedInput schema / properties / max_items / title
```
Removed value: -"Max Items"
```

changedInput schema / properties / max_tokens / description

Previous value: -"Approximate maximum response size."New value: +"Approximate token budget for the rendered context pack."

removedInput schema / properties / max_tokens / title
```
Removed value: -"Max Tokens"
```

removedInput schema / properties / memory_type

Removed value: -{
-  "default": "auto",
-  "description": "Memory type/category filter or value, such as episodic, identity, procedural, semantic, working, auto, or %.",
-  "title": "Memory Type",
-  "type": "string"
-}

removedInput schema / properties / output_json

Removed value: -{
-  "default": false,
-  "description": "Return a machine-readable JSON response instead of a human-readable summary.",
-  "title": "Output Json",
-  "type": "boolean"
-}

removedInput schema / properties / path_filter

Removed value: -{
-  "default": "%",
-  "description": "Memory path filter; % matches all paths.",
-  "title": "Path Filter",
-  "type": "string"
-}

removedInput schema / properties / prefer_working

Removed value: -{
-  "default": true,
-  "description": "Whether to prioritize working/session-state memories in retrieval.",
-  "title": "Prefer Working",
-  "type": "boolean"
-}

changedInput schema / properties / query / description

Previous value: -"Natural-language question or search text."New value: +"Natural-language query used to rank memories for the context pack."

removedInput schema / properties / query / title
```
Removed value: -"Query"
```

removedInput schema / properties / scope

Removed value: -{
-  "default": "",
-  "description": "Optional scope that narrows memory access; leave blank for the token default.",
-  "title": "Scope",
-  "type": "string"
-}

removedInput schema / properties / team_id

Removed value: -{
-  "default": "",
-  "description": "Optional team/workspace identifier for team-scoped memory access.",
-  "title": "Team Id",
-  "type": "string"
-}

removedInput schema / title

Removed value: -"recall_contextArguments"

removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
removedOutput schema / title
```
Removed value: -"recall_contextOutput"
```

First observedJun 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds genuinely non-obvious behavior on top: 'memories that do not fit are omitted and reported, so raise max_tokens or use recall when you need the records themselves.' This discloses a truncation-with-reporting trait that annotations cannot express.

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?

Three sentences with zero waste: purpose first, usage routing second, behavioral caveat third. Every sentence earns its place and the most decision-relevant information (what it does, when to pick it) is front-loaded.

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 21-parameter tool, the definition is complete for selection and invocation: output schema exists, so return values need no explanation, and the schema covers all parameter semantics at 100%. A small gap is that the description never mentions the structured-vs-rendered output option (output_json) or time-window capabilities, though these are well covered in the schema itself.

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 the baseline of 3 applies; the schema's parameter descriptions are unusually rich, with trigger conditions and model responsibilities for each field. The main description adds only marginal parameter context by tying max_items/max_tokens to the omission-and-report behavior. It correctly does not duplicate the schema's work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource pair ('Build a read-only, bounded context pack from multiple relevant memories') and immediately distinguishes itself from siblings: 'use recall for a quick best-effort lookup or get_project_context for a whole-project snapshot.' An agent can tell this tool apart from its nearest alternatives without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use criteria are given ('when an answer needs several memory items or scoped/path-filtered context') along with named alternatives and the conditions that route to them ('use recall for a quick best-effort lookup'). The guidance is actionable and leaves nothing to inference.

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

All XMemo tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.