clear_namespace
Delete all memories in a namespace.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| namespace | Yes | Namespace to clear |
agent-memory
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility for disclosing the destructive nature. It says 'Delete all memories' but does not mention that this is permanent, irreversible, or that it affects the entire namespace without confirmation. For a high-impact destructive operation, this is a significant gap.
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?
The description is a single clear sentence with no wasted words. It precisely conveys the action and object in a concise manner.
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?
While the tool is simple in structure, it performs a destructive bulk operation. The description lacks essential context such as irreversibility, behavior on non-existent namespaces, and any safety warnings. Given the absence of annotations and output schema, the description should carry more load to be complete.
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?
The schema covers 100% of the parameters, and the description for namespace ('Namespace to clear') is minimal but adequate. The description itself adds no extra semantic detail beyond the schema, so the baseline of 3 is appropriate.
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 clearly states a specific action and resource: 'Delete all memories in a namespace.' The phrase 'all memories' distinguishes it from the sibling tool delete_memory, which presumably deletes a single memory. No ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not provide any guidance on when to use this tool versus alternatives. It does not mention that it should be used for bulk clearing rather than iterating with delete_memory, nor does it state any prerequisites or warnings. Usage is only implied by the content.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: store, retrieve by ID, search, delete by ID, and clear a namespace. No two tools overlap in functionality or target different granularities.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with clear verbs (store, get, search, delete, clear) and nouns (memory, memories, namespace). The slight pluralization in search_memories is natural and does not disrupt consistency.
Tool Count5/5
Five tools is a well-scoped set for an agent memory system, covering the essential operations without unnecessary bloat or redundancy.
Completeness4/5
The surface covers create (store), read (get, search), and delete (delete, clear) for memories. A direct update operation is missing, but users can work around it by deleting and re-storing, so the gap is minor.