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 mark destructiveHint true; description confirms deletion by key. Adds context like pairing with remember/recall but doesn't detail error handling or idempotency behavior beyond 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 sentences, no fluff, front-loaded with purpose and usage guidelines.
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 the tool's simplicity: single parameter, no output schema. Description covers purpose, usage, and related tools.
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% and the parameter description is clear; the tool description adds no additional meaning beyond the 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 action ('Delete a previously stored memory by key') with a specific verb and resource, and distinguishes itself from sibling tools like '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 the tool (context stale, task done, clear sensitive data) and mentions paired tools, guiding proper selection.
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 due to detailed descriptions, but there is potential confusion among the many Polymarket and pipeworx-related tools. The Gong-specific tools are clearly separated.
Naming conventions are mixed: some use snake_case, others camelCase, and there is inconsistency between groups (e.g., gong_* vs. polymarket_*). However, within each subgroup, naming is consistent.
35 tools is high for coherence. The server covers multiple domains (Gong calls, data research, betting), leading to an overloaded toolset that could be streamlined into fewer, more general tools.
The toolset is comprehensive for its intended use cases, covering Gong call management, a wide array of data lookups, and Polymarket betting analysis. Minor gaps exist, such as limited CRM features beyond calls.