forgetDelete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Memory key to delete |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate destructiveHint=true and readOnlyHint=false, consistent with deletion. Description adds context about clearing sensitive data and stale context. Could mention if deletion is permanent or reversible, but overall good.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences efficiently convey purpose, usage, and relation to siblings. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool is simple with one parameter and no output schema. Description fully covers what the agent needs to know for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with one parameter 'key' described as 'Memory key to delete'. Description doesn't add new meaning beyond schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states 'Delete a previously stored memory by key', providing specific verb (Delete) and resource (memory by key). It distinguishes from siblings 'remember' and 'recall' by mentioning them, making the tool's purpose clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says 'Use when context is stale, the task is done, or you want to clear sensitive data' and suggests pairing with 'remember' and 'recall', offering clear when-to-use and alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes with detailed descriptions; however, the family of ask_pipeworx tools (beta, grounded) and deep_research could cause selection ambiguity despite clear documentation.
Tool names lack a consistent pattern; they mix imperatives, descriptive nouns, and domain prefixes. While overall readable, the lack of uniformity makes it harder to predict naming conventions.
34 tools is on the higher side but still within reasonable range given the broad scope (data queries, prediction markets, scraping, subscriptions, memory). Each tool appears purposeful, though some consolidation (e.g., ask_pipeworx variants) could reduce count.
The tool set covers a wide range of tasks from data querying to prediction market analysis and entity management. Minor gaps might exist (e.g., no direct social media data), but the overall coverage is extensive and sufficient for the platform's purpose.