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 context about clearing sensitive data but does not introduce new behavioral details beyond what annotations convey.
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 sentences front-loading purpose, usage, and sibling context. No extraneous content.
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 one-parameter deletion tool, the description covers purpose, usage guidelines, and relationship to sibling tools. No output schema needed.
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 clear description for the single parameter 'key'. The tool description adds no additional parameter information, so baseline score 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 and resource. Distinguishes from siblings by mentioning 'Pair 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?
Provides clear use cases: 'when context is stale, the task is done, or you want to clear sensitive data.' Lacks explicit when-not-to-use but is sufficiently directive.
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; however, 'ask_pipeworx' and 'ask_pipeworx_grounded' are very similar, and 'polymarket_edges' vs 'polymarket_edge_tracker' could cause confusion. The real estate tools (altos_active_listings, altos_new_listings, altos_pending_sales) are clearly differentiated by status.
Tool names use snake_case and are descriptive, but prefixes vary (altos_, polymarket_, ask_pipeworx, etc.) and patterns like 'entity_profile' or 'generate_llms_txt' don't follow strict verb_noun. Overall, naming is fairly consistent and readable.
36 tools is high but justifiable given the broad scope (real estate, prediction markets, SEC/FDA data, etc.). Some utility tools (list_subscriptions, pipeworx_feedback) could be integrated, but the count is borderline heavy for a single server.
The server covers multiple domains thoroughly with tools for real estate, company profiles, prediction markets, and general data queries. Minor gaps exist (e.g., no dedicated tool for FDA drug details beyond ask_pipeworx), but meta-tools like deep_research fill many needs.