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.
Input schema / examplesAdded value: +[
+ {
+ "key": "user_research_topic"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows it is a destructive write operation. The description adds valuable context about what kind of data to clear (sensitive data, stale context) and that it removes saved memories. This goes beyond the structured annotation hints without contradicting them.
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?
The description is two sentences, front-loaded with the primary action, followed by usage guidance and related tools. Every word earns its place with no filler or repetition.
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?
For a simple one-parameter tool with a complete schema and annotations, the description covers what the tool does, when to use it, and how it relates to siblings. No output schema is present, but a simple deletion tool does not require return-value details. The description is fully adequate for tool selection and 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 the 'key' property described as 'Memory key to delete'. The description's phrase 'by key' adds little beyond the schema. Baseline score of 3 is appropriate because the schema fully documents the parameter, and the description does not need to compensate.
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?
The description uses a specific verb ('Delete') and resource ('previously stored memory by key'), clearly distinguishing it from sibling tools like 'remember' and 'recall'. It exactly states the core function without ambiguity.
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?
The description provides explicit use cases: 'when context is stale, the task is done, or you want to clear sensitive data'. It also mentions pairing with 'remember and recall', giving relational context. However, it does not explicitly state when NOT to use the tool, which would make it a 5.
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.
Several tools overlap heavily: ask_pipeworx_beta is currently identical to ask_pipeworx, and find_related with syn/rhy options duplicates find_synonyms and find_rhymes. The six Polymarket tools and four entity-research tools also have fuzzy boundaries, so agents will struggle to reliably pick the right one.
Conventions are mixed: most tools follow verb_noun (ask_, find_, compare_, validate_) but several are bare nouns or noun phrases (entity_profile, recent_alertes, recent_changes) and others are bare verbs (remember, forget, subscribe, unsubscribe). The server name 'words' matches only five of 36 tools, adding further confusion about what to expect here.
36 tools is well into the heavy range, and the set bundles word lookups, a universal data router, six Polymarket tools, memory, subscriptions, and meta-utilities under one server. Many of these would be better split into dedicated, purpose-scoped servers.
For the dominant data-research and prediction-market scope, the surface is strong: grounded lookups, deep reseach, entity profiles, compareions, change feeds, claim verification, edge scanners, fill-risk checks, subscriptions, and memory are all covered. Minor gaps exist: taking 'words' literally there is no defintion or spelling tool, and there is no generic open-web search, but as a data-research toolkit it is quite complete.