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?
The description adds context beyond annotations, such as the memory being 'previously stored' (implying the key exists) and the use case for clearing sensitive data. Annotations already indicate destructive and idempotent behavior, but the description enriches understanding without 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?
The description is a single sentence that efficiently conveys the core action, usage guidelines, and complementary tools. No redundant or unnecessary text.
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 single-parameter tool with no output schema, the description covers all necessary aspects: purpose, usage context, and relationship to siblings. Annotations handle behavioral details, making the definition complete.
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?
The input schema has 100% coverage with a clear description of the 'key' parameter ('Memory key to delete'). The description adds minimal extra meaning ('by key'), so the baseline score of 3 is appropriate.
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 explicitly states the action ('Delete') and the resource ('previously stored memory by key'). It distinguishes itself from sibling tools by mentioning pairing with 'remember' and 'recall', making the purpose clear and differentiated.
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 provides concrete scenarios for when to use the tool: 'Use when context is stale, the task is done, or you want to clear sensitive data.' It also advises pairing with 'remember' and 'recall', offering clear guidance on usage.
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.
Multiple tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded all performing similar data lookups. Additionally, many tools focus on prediction markets and arbitrage, which are unrelated to the server's implied Go development domain, causing confusion.
Tool names follow inconsistent conventions: some use snake_case (e.g., 'latest_version', 'list_versions'), some use underscores in longer names (e.g., 'ai_visibility_check', 'ask_pipeworx_grounded'), and some use colons in descriptions but not in names. This mix reduces predictability.
With 35 tools, the count is high for a server named 'Pkg Go Dev' that only offers a few Go module-related tools (e.g., get_go_mod, list_versions). The majority are unrelated Pipeworx tools, making the scope mismatched and excessive.
The tool set severely lacks coverage for Go development tasks. It only includes basic module lookup tools (version listing, mod retrieval) but misses essential operations like dependency analysis, build commands, or testing. The vast majority of tools cover unrelated domains (prediction markets, company profiles, etc.), leaving the server incomplete for its intended purpose.