Skip to main content
Glama

Analyze XMemo memory text

analyze_memory_text
Read-onlyIdempotent

Count how often a word or phrase appears in your memories, with optional grouping by month, agent, or location.

Instructions

Count a word or phrase across XMemo memories, optionally grouped by month, agent, location, or type. Call this when the user asks how often a word/topic appears.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoOptional scope that narrows memory access; leave blank for the token default.
sinceNoOnly include memories or activity on or after this ISO 8601 timestamp.
untilNoOnly include memories or activity on or before this ISO 8601 timestamp.
phraseYesExact word or phrase to count across visible XMemo memories.
group_byNoOptional grouping: none, month, agent, location, memory_type, type, source, path, bucket, day, or comma-separated advanced fields.none
match_modeNoHow to match phrase: exact, case_insensitive, or regex_lite.exact
memory_typeNoMemory type/category filter or value, such as episodic, identity, procedural, semantic, working, auto, or %.%
output_jsonNoReturn a machine-readable JSON response instead of a human-readable summary.
path_filterNoMemory path filter; % matches all paths.%
max_examplesNoMaximum number of short snippets to include.
max_memoriesNoMaximum number of memories to inspect while analyzing text.
include_examplesNoWhether to include a few short matching memory snippets.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, making the behavior clear. Description does not contradict and adds minimal behavioral context beyond annotations.

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?

Two sentences with no wasted words. Front-loaded with purpose and usage trigger. Perfectly concise.

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?

Given 12 parameters, full schema coverage, output schema, and strong annotations, the description is adequately complete for a counting tool. Could mention group_by options briefly, but not necessary.

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 schema already documents all parameters. Description does not add meaning beyond what schema provides, earning baseline score.

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?

Description clearly states the tool counts a word or phrase across memories with optional grouping. This is a specific verb-resource pair that distinguishes it from sibling tools like search_memory or memory_stats.

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?

Explicit trigger 'Call this when the user asks how often a word/topic appears' provides clear context for use. Lacks explicit 'when not to use' or alternative tool names, but the trigger is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yonro/memory-os-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server