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. Description adds minimal extra behavioral context ('clear sensitive data') but no further details on permissions or side effects. Since annotations cover the safety profile, a baseline score of 3 is appropriate.
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?
Three concise sentences: one for purpose, one for usage context, one for related tools. No wasted words; all content 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 tool with one parameter, clear annotations, and no output schema, the description fully covers purpose, use cases, and related tools. 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?
Schema coverage is 100% with description 'Memory key to delete'. Description does not add extra meaning beyond the schema, so baseline score of 3 applies.
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?
Explicitly states 'Delete a previously stored memory by key' with a specific verb, resource, and method. Clearly distinguishes from sibling tools 'remember' (store) and 'recall' (retrieve).
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?
Provides clear contexts for use: stale context, completed tasks, clearing sensitive data. Mentions pairing with related tools. Does not explicitly state when not to use, but the positive guidance is strong.
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.
Most tools have distinct purposes, especially within the Polymarket and data query groups. However, the three ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and the overlap between deep_research and ask_pipeworx for broader questions could cause minor confusion.
Tool names follow some consistent prefixes (ask_pipeworx, polymarket_, scan_, recent_) but overall mix verb_noun, noun phrases, and standalone verbs (forget, recall, remember). This inconsistency reduces predictability, though the patterns are still readable.
32 tools is high but justifiable given the server's dual role as a Pipeworx data gateway and Polymarket analysis suite. Each tool serves a distinct function in the workflow, but the count borders on heavy and could be streamlined.
The tool set covers the full lifecycle for the server's domain: discovery, querying, grounded answers, entity resolution, company profiles, fact-checking, prediction market analysis, memory, and monitoring. Minor gaps exist (no account management or direct data modification), but these are out of scope for a read-only data interface.