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. The description adds context about clearing sensitive data and pairing, but doesn't introduce new behavioral traits beyond confirming 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, no unnecessary words. The description is front-loaded with the core action and efficiently includes usage guidance.
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 tool with one parameter, no output schema, and informative annotations, the description covers the operation, use cases, and relationship to sibling tools. Nothing essential is missing.
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 input schema already describes the 'key' parameter as 'Memory key to delete' (100% coverage). The description adds no additional semantic details beyond what the schema provides.
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 'Delete a previously stored memory by key', specifying the action (delete) and resource (memory by key). It distinguishes from siblings 'remember' and 'recall' by implying storage and retrieval operations.
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 explicit usage scenarios: 'when context is stale, the task is done, or you want to clear sensitive data'. Also pairs with 'remember' and 'recall', but does not explicitly state when not to use.
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.
Many tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer factual questions through similar routing; the polymarket_* tools and entity_profile/compare_entities/recent_changes also cover the same ground. The server is named Pubchem but most tools are unrelated, adding another layer of confusion.
All tool names are snake_case and mostly follow verb_noun (search_by_name, get_compound, create_subscription, etc.). Minor deviations exist like entity_profile and recent_alerts being noun-first, and the pipeworx_*/polymarket_* prefixes make the set feel more like multiple products than one coherent API.
35 tools is a large surface, and only 4 (search_by_name, get_compound, get_classification, get_synonyms) actually belong to PubChem. The other 31 tools form a broad Pipeworx/prediction-market toolkit that seems unrelated to the server's stated name and purpose.
For a PubChem server the coverage is minimal: basic name->CID resolution, compound properties, classification, and synonyms, but no formula search, bioassay, spectra, or list/search by other identifiers. The Pipeworx tools are extensive for general data querying but require accounts/keys for full use, so anonymous agents hit incomplete workflow dead ends.