Skip to main content
Glama
kubainter

BoteX

by kubainter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

search_memory

Searches the workspace Memory Vault (<workspace_dir>/.botex/memory/) by keyword query, tag, or entry kind (context, decision, handoff, lesson).

Instructions

Searches the workspace Memory Vault (<workspace_dir>/.botex/memory/)
by keyword query, tag, or entry kind (context, decision, handoff, lesson).

Args:
    workspace_dir: Workspace root directory. Empty = engine.default_workspace
           from the config, else the server's current directory.
    query: Free-text search string matched against title, content, and tags.
    tag: Filter by specific tag.
    kind: Filter by entry kind ('context', 'decision', 'handoff', 'lesson').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNo
kindNo
queryNo
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.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the storage path and the fallback chain for an empty workspace_dir (config default workspace, else server CWD), but says nothing about how filters combine, result ordering/limits, or that the call is a non-mutating read.

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?

Front-loaded with the one-line purpose before the Args block, and each parameter line earns its place. The docstring-style 'Args:' formatting is functional rather than elegant, but nothing is wasted.

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

Completeness3/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 four parameters are covered. Still missing are the filter-combination semantics (AND vs OR) and any guidance on relating this tool to read_memory/save_memory, which leaves real gaps for a discovery tool.

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%, so the description does the full job: it explains all four parameters, gives the empty-string default semantics for workspace_dir, and enumerates the valid kind values (context, decision, handoff, lesson) that the schema fails to express as an enum.

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 specific verb and resource ('Searches the workspace Memory Vault') and names the three filter dimensions (query, tag, kind). It is clearly distinguishable in intent from save_memory and read_memory, though it never names those siblings 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?

Usage is implied by describing the filter modes, but there is no explicit when-to-use/when-not guidance and no routing against the obvious alternatives read_memory and save_memory. An agent must infer that this is the discovery tool and the other two are point read/write.

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