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 declare destructiveHint=true and idempotentHint=true. The description adds useful context about clearing sensitive data, which goes beyond the structured hints. No contradiction detected.
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 that are front-loaded with the action ('Delete a previously stored memory by key'), followed by usage guidance. Every word earns its place.
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 one-parameter tool with no output schema, the description covers the action, usage scenarios, and relationship to sibling tools, making it fully self-contained.
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%, so the schema already documents the 'key' parameter completely. The description mentions 'by key' but adds no additional syntax or behavioral detail beyond the schema.
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 uses a specific verb 'Delete' with a clear resource ('previously stored memory by key'), and it distinguishes itself from sibling tools by mentioning pairing 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?
Explicitly states when to use: 'when context is stale, the task is done, or you want to clear sensitive data'. Also names related tools ('remember' and 'recall') to clarify its complementary role.
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 are clearly from distinct domains (Pexels media, Pipeworx data, Polymarket betting, utility), but within each domain there is significant overlap (e.g., ask_pipeworx vs ask_pipeworx_grounded vs deep_research, or numerous polymarket tools). Detailed descriptions help differentiate, but some tools could still be confused.
Naming conventions vary: some tools use verb_noun (ask_pipeworx, compare_entities), others are single-word (photo, video), and some mix patterns (photo_curated vs photo_search). The Pexels subset is consistent, but the overall set includes tools from other ecosystems with different styles.
With 38 tools, the set is bloated for a Pexels server. Only 8 tools are actually Pexels-related; the rest are Pipeworx data query, Polymarket betting, and utility tools. This mismatch makes the count inappropriate for the stated server purpose.
For the Pexels domain, the tool set covers search, fetch, and collections for both photos and videos, which is adequate. The unrelated tools add bloat but don't create gaps in the Pexels functionality. Minor missing features like uploads or editorial content are not critical.