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 provide destructiveHint=true and idempotentHint=true. The description adds context about clearing sensitive data but does not elaborate on side effects beyond deletion.
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 wasted words. Front-loaded with action and resource.
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?
Single parameter fully documented in schema. Description covers purpose, usage, and relationships. No output schema needed for this straightforward tool.
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?
The schema already describes the 'key' parameter as 'Memory key to delete' (100% coverage). The description adds no additional semantic 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 verb 'Delete' and resource 'previously stored memory by key'. It distinguishes from sibling tools 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 provides when to use: 'when context is stale, the task is done, or you want to clear sensitive data'. Also suggests pairing with other 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.
The set mixes near-synonymous routers (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded), overlapping discovery tools (discover_tools, suggest_questions), and several prediction-market scanners (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker) whose boundaries are easy to blur. The six onedrive_* tools are distinct, but they are buried in an unrelated toolkit where multiple tools appear to address the same task.
Naming is split across several conventions: onedrive_*, polymarket_*, and pipeworx_* form consistent clusters, but top-level tools use bare verbs (remember, recall, forget), noun phrases (entity_profile, compare_entities), and varied styles (deep_research, generate_llms_txt, validate_claim). The pattern is readable within clusters, but not predictable across the server.
37 tools is heavy, and the vast majority have nothing to do with the server's name 'Onedrive' — only 6 of 37 target OneDrive, while 31 span Pipeworx data, Polymarket betting, memory, and web utilities. This is a sprawling multi-domain bundle rather than a focused server.
As a OneDrive server, the surface is severely incomplete: it offers read-only coverage (list, search, get, profile, shared) but no upload, create, update, move, copy, delete, or share operations, and binary Office/PDF content returns unreadable bytes. The Pipeworx tools are individually comprehensive, but they do not fill the basic lifecycle gaps for the server's apparent file-management domain.