Skip to main content
Glama
kubainter

BoteX

by kubainter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

save_memory

Saves a persistent context note, architectural decision, task handoff, or lesson into the workspace Memory Vault (<workspace_dir>/.botex/memory/). Masks secrets and provides directory isolation.

Instructions

Saves a persistent context note, architectural decision, task handoff, or lesson
into the workspace Memory Vault (<workspace_dir>/.botex/memory/).
Masks secrets and provides directory isolation.

Args:
    title: Short descriptive title of the memory entry.
    content: Detailed markdown notes, architectural rationale, or handoff context.
    workspace_dir: Workspace root directory. Empty = engine.default_workspace
           from the config, else the server's current directory.
    kind: Entry category ('context' | 'decision' | 'handoff' | 'lesson').
    tags: Optional list of keyword tags for filtering and discovery.
    memory_id: Optional custom identifier (alphanumeric/hyphen/underscore). Auto-generated if omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNocontext
tagsNo
titleYes
contentYes
memory_idNo
workspace_dirNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • changedInput schema / properties / workspace_dir / default
      Previous value: -"."New value: +""
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose non-obvious behaviors: automatic secret masking, directory isolation, and memory_id auto-generation when omitted. It does not say what happens on an ID/title collision (overwrite vs. error), nor anything about permissions or retention, which are important for a persistent write.

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 lead sentence front-loads purpose and destination, followed by a tight Args list where each entry is one sentence. No filler, though the multi-line block format is slightly verbose relative to the information conveyed.

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?

An output schema exists so return values need not be explained, and all input parameters are covered along with useful side-effect notes (secret masking, isolation). The remaining gap is usage routing against the read/search siblings and collision behavior, which keeps it short of complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description documents all six parameters with meaning beyond the bare types: it explains the kind categories, that tags are for filtering/discovery, that memory_id must be alphanumeric/hyphen/underscore and is auto-generated if omitted, and the fallback rules for workspace_dir. Strong compensation, though the markdown format of content could be stated more precisely.

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?

States a concrete verb and resource ('Saves a persistent context note... into the workspace Memory Vault') and names the exact storage path plus the four entry categories. It clearly occupies the write slot opposite the read_memory/search_memory siblings, though it never names those alternatives explicitly.

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 kind values ('context' | 'decision' | 'handoff' | 'lesson') implicitly signal when each entry type applies, which gives partial usage guidance. However, there is no explicit statement of when to use save_memory versus search_memory/read_memory, no when-not conditions, and no prerequisites.

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