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?
Description confirms deletion, aligning with destructiveHint=true annotation. However, it adds no extra behavioral context beyond what annotations already declare.
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, front-loaded with purpose, no extraneous information.
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 tool with clear annotations, the description is complete: explains purpose, usage context, and relationship to siblings.
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%, so the schema already documents the key parameter. Description does not add 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?
Description clearly states the tool deletes a stored memory by key, specifying verb, resource, and identifier. It distinguishes from siblings 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: when context is stale, task is done, or to clear sensitive data. Also suggests pairing with remember and recall.
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.
Several tools blur together: ask_pipeworx_beta currently duplicates ask_pipeworx exactly, ask_pipeworx/ask_pipeworx_grounded/deep_research/validate_claim all route natural-language questions to data sources, and the prediction-market tools (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, bet_research) have fuzzy boundaries. The detailed descriptions help, but an agent can easily misselect among them.
All names are lowercase snake_case and the rxnorm_, polymarket_, and pipeworx_ prefixes create readable groupings, but the set mixes imperative verb-object names (validate_claim, list_subscriptions), noun-phrase names (entity_profile, recent_alerts), and bare verbs (remember, forget). It is readable but not a predictable uniform naming convention.
35 tools is in the too-many band for a coherent server, and the Rxnorm identity makes it worse: only 4 tools are actually RxNorm-specific while 31 are unrelated Pipeworx, prediction-market, memory, and utility tools. A focused RxNorm server would need a fraction of this surface.
The four rxnorm_* tools plus resolve_entity cover the main RxNorm lookup flow (search, properties, related, NDC), so the core is not broken. But the set lacks a reverse NDC-to-concept lookup and the 31 non-RxNorm tools do not complete any single coherent domain, leaving notable gaps relative to the server's stated purpose.