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.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description aligns with annotations (destructiveHint=true). Adds context about clearing sensitive data and removing stale context, going beyond what annotations provide. No contradiction.
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, no wasted words, front-loaded with action. Highly 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 provides complete context: purpose, usage, and behavior. No gaps.
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?
Single parameter 'key' has schema description 'Memory key to delete'. Schema coverage is 100%, so description adds no extra meaning beyond 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 clearly states the tool deletes a stored memory by key, using a specific verb and resource. It distinguishes itself from siblings by mentioning '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, task is done, or to clear sensitive data. Also advises pairing with related tools.
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.
Several tool clusters have fuzzy boundaries: ask_pipeworx and ask_pipeworx_beta are described as currently identical, and ask_pipeworx/deep_research/validate_claim overlap for factual research. Polymarket_arbitrage, polymarket_edges, and bet_research also all surface betting opportunities, while ai_visibility_check and scan_competitor_ai_presence serve nearly the same purpose.
Names are readable and mostly snake_case, but the pattern is mixed: doffin_* and polymarket_* use domain-prefixed nouns, ask_pipeworx* uses verb+product, and remember/recall/forget/subscribe are bare verbs. There is no single predictable verb_noun convention, though each internal cluster is somewhat consistent.
34 tools is heavy for a server named Doffin, and only three tools actually relate to Norwegian procurement. The remaining surface is mostly general Pipeworx data access, prediction-market analysis, and memory utilities, which feels like several servers bundled under one misleading name.
For Doffin read-only access, search + recent + notice detail covers the core workflow well. However, the server's actual domain is fragmented across procurement, Pipeworx research, prediction markets, memory, and subscriptions, which makes coverage difficult to reason about and leaves minor gaps such as no subscription update capability.