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 the tool as destructive, and the description reinforces this by stating the deletion action. It adds context about clearing sensitive data, which goes beyond annotations. 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, no wasted words. First sentence states the core action, second gives usage guidance and hints at siblings. Excellent conciseness.
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 deletion tool with one parameter and no output schema, the description is sufficiently complete. It covers purpose, usage context, and related tools. Could mention error handling for missing keys, but that's minor.
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 the 'key' parameter well-described. The description adds little extra beyond 'by key', which is already in the schema. 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 clearly states the action ('Delete a previously stored memory by key') and distinguishes this tool from siblings ('remember' and 'recall'), making the purpose unambiguous.
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?
Explicit usage conditions are given ('when context is stale, the task is done, or you want to clear sensitive data'), helping the agent decide when to invoke. Could be improved by also stating when not to use, but the guidance is clear.
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.
Each tool has a clearly distinct purpose described in detail. Even tools like ask_pipeworx, ask_pipeworx_grounded, and deep_research are differentiated by hallucination resistance, account requirements, and use cases. Polymarket tools are each specialized (arbitrage, edges, fill risk, etc.). No two tools appear to do the same thing.
All tool names follow snake_case consistently. They use descriptive verb-noun patterns (e.g., ask_pipeworx, bet_research, compare_entities, subscribe). No mixing of conventions or ambiguous names.
32 tools is on the higher side but justified by the server's broad scope covering company research, prediction markets, data lookups, memory, subscriptions, and more. Each tool serves a distinct function, though the count might feel slightly heavy for a single server.
The toolset covers core workflows for company analysis, prediction market operations, data retrieval, and system management (memory, subscriptions). Minor gaps exist (e.g., no direct tool for non-company entity profiles beyond drugs), but the overall surface is comprehensive for the intended multi-purpose assistant.