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 include destructiveHint: true and idempotentHint: true. Description reinforces deletion and clearing sensitive data. Adds context that it clears 'data the agent saved earlier', but could mention irreversibility. No contradictions.
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 waste. Front-loads the action and provides context immediately.
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?
Complete for a one-parameter tool with no output schema. Describes purpose, usage context, and relationship to siblings.
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'. Description adds little beyond schema but reinforces that it's a previously stored memory. Baseline 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?
Description clearly states 'Delete a previously stored memory by key' with specific verb and resource. Distinguishes itself from siblings by mentioning pairing with 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, the task is done, or you want to clear sensitive data'. Also mentions pairing with related tools for context.
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 clearly distinct purposes, especially in networking and domain-specific queries. However, the multiple `ask_pipeworx` variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and `deep_research` have overlapping functionality, which could cause occasional misselection.
Tool names use inconsistent conventions: some are concatenated (geoloc, whois), some use underscores (abuse_contact, as_overview), and some are multi-word (scan_competitor_ai_presence, ask_pipeworx_grounded). No consistent pattern across the set.
39 tools is high for a single server, but justified by the broad scope covering networking, finance, prediction markets, AI visibility, and more. However, many tools are meta-tools for the Pipeworx ecosystem, making the set feel slightly bloated.
The server covers an exceptionally wide range of domains comprehensively, with tools for networking, company data, FDA datasets, prediction markets, weather, news, and more. It includes memory and subscription management, leaving few obvious gaps for its stated data-retrieval purpose.