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 already indicate destructive and idempotent behavior. The description adds context about sensitive data clearing, but doesn't specify behavior for missing keys or confirm idempotency explicitly.
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 with no wasted words: first states purpose, second provides usage guidance and sibling pairing.
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 simple single-parameter tool, the description fully covers purpose, usage, and pairing with siblings, leaving no gaps.
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% and the description repeats the parameter name without adding new detail; baseline score 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?
The description clearly states the action ('Delete a previously stored memory by key') and distinguishes from sibling tools by positioning itself as the deletion counterpart to 'remember' and 'recall'.
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 lists when to use (stale context, task done, clear sensitive data) and indirectly when not (use remember/recall instead), providing clear decision guidance.
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.
Tools have distinct purposes described in detail; however, several query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research) overlap in general domain, causing minor ambiguity.
No consistent naming pattern: mix of verb_noun (ask_pipeworx), noun_verb (bet_research), descriptive (entity_profile), and inconsistent use of underscores/camelCase.
32 tools is excessive for a single server, especially when the server name 'Passwordgen' only covers 2 tools; the rest form a sprawling data platform that could be split.
As a password generator it is missing features like strength checking; as a data platform it covers queries and subscriptions but lacks write capabilities, leaving notable gaps.