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 provide destructive and idempotent hints; description confirms deletion but adds minimal behavioral context 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 plus a pairing note, no fluff, highly concise.
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 1-param tool with no output schema, the description provides complete context: what, when, how, 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 covers the single parameter fully; description adds no additional meaning beyond the schema's 'Memory key to delete'.
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 tool deletes a memory by key, distinguishing it from siblings 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 (stale context, done task, clear sensitive data) and pairs with other tools.
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 three ask_pipeworx variants are near-identical (the beta is currently an exact copy of the stable router), and ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim all route natural-language questions to the same underlying source catalog. The six polymarket_* tools also heavily overlap in opportunity detection, though some clusters like memory and subscriptions are clearly separated.
The naming is mostly snake_case but mixes conventions: verb_noun (list_subscriptions, resolve_entity), noun-first (entity_profile, bet_research), metadata-style prefixes (pipeworx_trending, polymarket_edges), and bare verbs (remember, recall, forget). It is readable but does not follow one predictable pattern across the set.
33 tools is excessive for a server nominally named Open Notify, and the count is inflated by redundant ask_pipeworx variants and six closely-related Polymarket tools. The broad data-gateway scope could justify a large catalog, but the set feels bloated and unfocused rather than deliberately scaled.
For the apparent Open Notify domain, only astros and iss_now fit, and core ISS functionality like pass predictions is missing. The wider data-lookup surface is extensive, but the inclusion of unrelated memory, subscription, npm-scanning, and llms.txt tools means no single domain gets coherent lifecycle coverage.