Skip to main content
Glama

forget_conversation

Deletes a named conversation's history from the remote Ollama session, or clears all saved conversations when no name is provided.

Instructions

Drop a named conversation's history, or all of them if no name is given.

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": "forget_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden. It does disclose the dangerous default (omitting the parameter drops every conversation), but says nothing about whether the deletion is permanent, whether it affects only the caller's view, what permissions are required, or what the call returns.

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?

A single well-formed sentence with the destructive default front-loaded after the primary action. No wasted words; slightly more structure (e.g., explicit warning wording) would help for a destructive operation.

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?

The tool is simple (one optional param, no output schema), and the description covers the core action plus the all-conversations default. For an unannotated destructive operation it should still state permanence and identifier format 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?

Schema coverage is 0%, so the description must compensate. It usefully defines the null/omitted case as "all conversations," which is the critical semantic of the single parameter, but it never specifies whether the value is a conversation name, ID, or slug, leaving identifier format ambiguous.

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?

Names a specific verb ("Drop") and resource ("a named conversation's history"), and states the scope variant when no name is supplied. It is distinguishable from the chat/models siblings, though it never names or contrasts them.

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 only implied: an agent can infer this is the tool for discarding history. The one explicit usage-relevant rule is the omission semantics (no name = all), which is stated, but there is no guidance on when to prefer this over continuing a chat or how to confirm intent before a broad wipe.

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