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 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, so the description adds limited extra behavioral context. The description mentions clearing sensitive data, which provides some additional insight but is not highly detailed.
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, front-loaded with the action and resource, no extraneous information. Every sentence serves a purpose.
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 purpose, usage context, and pairing with related tools. It is fully adequate.
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 a clear description for the 'key' parameter. The description only says 'by key', adding minimal meaning beyond the schema's 'Memory key to delete'.
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?
Description clearly states 'Delete a previously stored memory by key', specifying the verb and resource. It also mentions the sibling tools 'remember' and 'recall', distinguishing the tool's purpose from those.
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'. It pairs with 'remember' and 'recall' but does not explicitly state when not to use this tool or provide alternatives beyond the pairing.
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 have overlapping purposes, especially the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and the Polymarket cluster (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread). Additionally, discover_tools and suggest_questions both serve as discovery/onboarding tools, and ai_visibility_check vs scan_competitor_ai_presence are closely related. While descriptions are detailed, the boundaries between these tools are unclear, causing potential misselection.
All tool names use lowercase snake_case with no camelCase or mixed styles. The naming follows a mostly consistent verb_noun or data_subject pattern (e.g., ask_pipeworx, list_subscriptions, validate_claim, artist_info, recent_alerts). Minor deviations exist, such as recent_alerts and user_top_tracks not beginning with a verb, but the overall pattern is predictable and readable.
40 tools is far too many for a server nominally about Last.fm; only 9 tools actually relate to its stated purpose. The remaining 31 tools cover unrelated domains (Pipeworx data routing, Polymarket betting, memory, subscriptions, etc.), making the set bloated and unfocused. Many tools are near-duplicates (ask_pipeworx, _beta, _grounded; four different polymarket_* analysis tools), inflating the count without adding distinct value.
Even within the Last.fm domain, the tool surface is incomplete: there is no artist search, album search, user profile info, recent scrobbles, loved tracks, or music recommendations. The unrelated Pipeworx/Polymarket tools, while individually comprehensive for their own domains, do not compensate for the lack of core Last.fm functionality given the server's stated purpose. The overall set is a fragmented mixture that leaves significant gaps for what the server name promises.