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 indicate destructive and idempotent behavior. The description adds no further behavioral details beyond the fact that it deletes a memory; it does not clarify what happens if the key does not exist or if there are any side effects. With annotations covering the key safety traits, the minimal extra context suffices.
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?
Two concise sentences: the first states the action, the second gives usage guidance. No extraneous information, and the key information is front-loaded.
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?
Given the low complexity (single required parameter, no output schema, no nested objects), the description covers the essential aspects. It could mention the expected behavior on success or failure (e.g., whether it returns anything), but the lack of an output schema reduces the need. Overall, it is adequately informative for an agent to use correctly.
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 provides 100% coverage with a description for the 'key' parameter ('Memory key to delete'). The tool description adds no additional meaning beyond what the schema already states, so the baseline score of 3 applies.
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?
Clearly states the action: delete a memory by key. Distinguishes itself from sibling tools 'remember' and 'recall' by pairing with them, making its role as the deletion function explicit.
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?
Provides explicit contexts for use: stale context, completed task, clearing sensitive data. Mentions alternative or complementary tools ('remember' and 'recall'), guiding when to use this tool versus others.
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.
Many tools have overlapping purposes, e.g., three tools for querying Pipeworx data (ask_pipeworx, ask_pipeworx_grounded, deep_research), and six tools for Polymarket prediction markets. The boundaries between them are unclear, causing potential for misselection.
Tool names are all snake_case but follow inconsistent patterns: some use verb_noun (get_hottest, get_newest), some are single verbs (remember, forget), and others are noun_noun (bet_research, polymarket_arbitrage). While readable, the lack of a consistent pattern adds confusion.
With 34 tools, the server is overloaded, especially given its name 'Lobsters' suggests a focus on that site, yet only 4 tools are Lobsters-related. The majority belong to Pipeworx, Polymarket, and generic utilities, making the scope extremely broad and unfocused.
For the implied domain of Lobsters, the tool set is incomplete (missing create/update/delete). For the broader domains (Pipeworx, Polymarket), the set is extensive but doesn't align with the server's name. The lack of a coherent domain leaves obvious gaps relative to any single purpose.