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, idempotentHint=true, and readOnlyHint=false. The description adds context about clearing sensitive data, which provides additional behavioral insight beyond the 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 with no wasted words. The purpose is front-loaded, and the usage guidance is clear and concise.
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 covers the purpose, usage context, and pairing with sibling tools. Complete and actionable.
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 has 100% coverage for the single parameter 'key' with description 'Memory key to delete'. The tool description does not add further parameter details, but the schema already covers it adequately.
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 "Delete a previously stored memory by key," providing a specific verb and resource. It distinguishes itself from sibling tools 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?
Explicitly tells when to use: "when context is stale, the task is done, or you want to clear sensitive data." Also recommends pairing with 'remember' and 'recall', indicating 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.
Tools cover a wide range of domains (TV, finance, betting, memory, etc.), each with detailed descriptions that help distinguish their purposes. However, some overlap exists between related tools like bet_research, polymarket_arbitrage, and polymarket_edges, though the descriptions clarify their distinct uses.
Most tool names follow a consistent verb_noun pattern with underscores (e.g., get_show, list_episodes, resolve_entity). A few tools use single imperative verbs (remember, recall, forget), which is a minor deviation but still clear.
The server has 31 tools, which is on the higher side. While each tool has a defined purpose, the scope seems too broad for a server named 'Tvmaze', as many tools are unrelated to TV (e.g., company analysis, betting, memory). A more focused set would improve coherence.
For a general-purpose data server, the tool set covers a wide range of tasks: TV show lookups, company research, betting analysis, memory management, and more. The inclusion of ask_pipeworx as a fallback for many queries compensates for missing specific tools. However, the TV-specific functionality is limited to search and schedule, missing details like cast or crew.