Skip to main content
Glama

Typebar (formerly SuperDocs)

clear_cross_session_memory

Delete the caller's cross-session memory note. Owner-scoped: a caller can only clear its OWN note. With no key this clears the account-level note; with a memory_key it clears that one end-customer's note. Idempotent (removed=0 if it didn't exist).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clear_cross_session_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
memory_keyNoClear ONE end-customer's stored memory (the cross_session_memory_key you send on chat). Omit to clear the account-level note (the B2C default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the owner-scoping authorization constraint ('can only clear its OWN note'), the default target when the key is omitted, and idempotency semantics including the `removed=0` outcome. It stops short of saying whether a cleared note is recoverable, which is the one behavioral gap for a destructive operation.

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?

Four short sentences, front-loaded with the verb and resource, then scoping, branch behavior, and idempotency in a sensible order. Slight overlap between the branch sentence and the schema's parameter description is the only waste.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by naming the return signal (`removed=0`). With one optional parameter and no annotations, the definition covers scope, defaults, authorization, and result semantics — nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the single parameter is already documented, but the description reinforces the contract by framing the two modes (account-level default vs. one end-customer) and tying memory_key to the cross_session_memory_key sent on chat. It adds clarifying meaning without redundant restatement.

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?

States a specific verb and resource — 'Delete the caller's cross-session memory note' — which no sibling tool touches (siblings cover documents, sessions, jobs, templates, attachments). An agent can identify the operation and distinguish it from the rest of the toolset immediately.

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?

Gives explicit branch conditions: no key clears the account-level note, with a memory_key it clears that end-customer's note. It does not name alternatives or when-not-to-use, but no sibling performs an overlapping operation, so the guidance is effectively complete for selection.

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.