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?
The description adds context beyond annotations by specifying that it deletes sensitive data and pairs with other memory tools. No contradictions with annotations (destructiveHint=true, idempotentHint=true). It doesn't detail error handling (e.g., missing key), but the idempotent hint covers that.
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 sentences, front-loaded with the core action, and no wasted words. Every sentence provides value.
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 tool with one parameter, no output schema, and good annotations, the description covers purpose, usage, and relationships. Nothing essential is missing.
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?
With 100% schema coverage, the description does not add significant meaning beyond the schema's 'Memory key to delete'. 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?
The description states 'Delete a previously stored memory by key', which is a specific verb and resource. It distinguishes itself from siblings like 'remember' and 'recall' by focusing on deletion.
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 scenarios for use: stale context, completed task, clearing sensitive data. It also suggests pairing with 'remember' and 'recall', giving clear guidance on when to use this tool.
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 (multiple ask_pipeworx variants, several polymarket tools, and similar research functions). The agent would struggle to pick the right tool among 36, especially with unclear boundaries between some tools.
Tool names lack a consistent pattern. The li_ prefix for LinkedIn tools is isolated; other tools use random prefixes (pipeworx_, polymarket_) or no prefix at all (ask_pipeworx, bet_research). Mix of verb_noun and noun structures.
36 tools for a server named 'Linkedin_ads' is excessive. Only 5 tools are actually LinkedIn ads-related; the rest are unrelated, making the server feel bloated and unfocused. A focused server would have 5-10 tools.
For the stated LinkedIn ads domain, the tool set is incomplete: missing create/update/delete campaigns, budget management, and targeting. While the server includes many other data tools, its advertised purpose is poorly served.