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?
Annotations already declare destructiveHint=true and idempotentHint=true. The description adds value by specifying what kind of data should be deleted (stale, sensitive) and implies permanence. No contradiction with annotations.
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 concise sentences, zero wasted words. First sentence states the action, second provides usage context. Efficient and well-structured.
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?
Given the tool's simplicity (single parameter, no output schema) and comprehensive annotations, the description fully covers purpose, usage, and behavioral context. No gaps remain for effective agent invocation.
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 single 'key' parameter described as 'Memory key to delete'. The description does not add additional semantic meaning beyond the schema, so 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?
Description clearly states 'Delete a previously stored memory by key' with a specific verb and resource. It also mentions pairing with 'remember' and 'recall', distinguishing its function among siblings. The usage context further clarifies purpose.
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 the agent saved earlier.' Also references alternatives by mentioning pairing with 'remember' and 'recall', providing clear guidance.
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, e.g., multiple ask_pipeworx variants, bet_research vs. polymarket_edges, and several entity/profile tools. An agent could easily misselect between similar tools despite detailed descriptions.
Tool names are inconsistent: some use snake_case (ask_pipeworx), some camelCase (ai_visibility_check), and verbs vary (ask, bet, compare, scan, validate). No clear naming convention is followed across the set.
With 34 tools, the server covers a broad range of functionalities for a platform like Pipeworx. While each tool seems justified, the count is on the higher end, potentially overwhelming for simpler use cases.
The tool set covers data retrieval, memory, subscriptions, Polymarket analysis, and utility functions comprehensively. Minor gaps exist (e.g., no direct user management) but core workflows are well-supported.