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 destructiveHint=true and readOnlyHint=false, so the description's 'Delete' action aligns without contradiction. It adds context about clearing sensitive data and stale context, going slightly beyond raw annotations. No explicit side effects mentioned, but annotations cover the destructive nature, so a 4 is appropriate.
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 core action, followed by practical usage context and sibling references. No wasted words; every sentence contributes 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?
Given the tool's simplicity (one required parameter, no output schema), the description fully covers purpose, usage, and safety context (with annotations). It is complete enough for an agent to select and invoke the tool 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 coverage is 100% with the parameter description 'Memory key to delete.' The description adds only the phrase 'previously stored' and 'by key,' which reinforces but does not significantly expand on the schema. Baseline 3 is justified as the schema carries the parameter meaning.
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 a specific verb and resource: 'Delete a previously stored memory by key.' This directly distinguishes it from sibling tools like remember and recall, making the tool's function unambiguous.
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?
Explicit usage contexts are provided: 'Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier.' It also advises pairing with remember and recall, offering clear guidance on when to use this tool relative to 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, but there is overlap among closely related Polymarket tools (e.g., bet_research, polymarket_edges, polymarket_arbitrage) and between ask_pipeworx and ask_pipeworx_grounded, which could cause misselection.
Tool names mix verb_noun, noun_verb, and descriptive phrases inconsistently (e.g., get_times vs listen_subscriptions vs bet_research), and while many use underscores, conventions vary, making patterns hard to predict.
With 32 tools, the server feels overloaded, covering distinct domains (sunrise, Pipeworx, Polymarket, memory, subscriptions) under one name, making it a 'Swiss army knife' rather than a focused toolset.
The server name suggests a narrow domain (sunrise/sunset) but only 2 of 32 tools address it, ignoring related weather data. While other domains are covered, operations lack depth (e.g., no subscription updates, no memory search).