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 provide destructiveHint=true; description confirms deletion and adds context about clearing sensitive data. No contradiction, but no additional behavioral details beyond annotations.
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: first states purpose, second gives usage guidance. No wasted words.
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 and no output schema, the description fully covers when and how to use it, especially with annotations present.
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 clear description for 'key'. The tool description does not add further meaning beyond what schema provides.
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 verb 'Delete' and resource 'previously stored memory by key'. It distinguishes from siblings by explicitly mentioning 'Pair with 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?
The description explicitly lists when to use: 'when context is stale, the task is done, or you want to clear sensitive data'. It also suggests pairing with siblings.
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.
The tool set is a mix of 5 Google Calendar tools and 31 unrelated Pipeworx tools (e.g., ask_pipeworx, deep_research, entity_profile). Even within Pipeworx, tools like ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded have highly overlapping purposes, making it very difficult for an agent to distinguish which tool to use.
Naming conventions are chaotic. The Google Calendar tools follow a consistent gcal_ prefix, but the rest use various patterns: pipeworx_*, polymarket_*, single words (remember, recall), and others (bet_research, scan_dependency). There is no overarching pattern.
With 36 tools, the count is high, but only 5 are relevant to Google Calendar. The remaining 31 tools are from a completely different domain (Pipeworx data access, Polymarket betting, etc.), making the tool count severely inappropriate for the server's stated purpose.
For Google Calendar, the tools provide basic CRUD (create, get, list, search, list_calendars) but lack update and delete functionality. The vast number of unrelated tools does not compensate for these gaps. The overall surface is incomplete for the calendar domain.