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 no new behavioral traits beyond stating deletion, which is consistent. It mentions 'clear sensitive data' as a use case but no additional details like permissions or irreversible effects.
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: purpose, when to use, and pairing suggestion. No fluff or redundancy. Every sentence adds value.
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 and no output schema, the description is complete. It covers purpose, usage context, and sibling relationships, and annotations cover safety properties.
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 single 'key' parameter described as 'Memory key to delete'. The description's 'by key' adds no new meaning beyond what the schema provides, so the baseline score of 3 is appropriate.
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 previously stored memory by key, distinguishing it from siblings 'remember' (store) and 'recall' (retrieve). The verb 'delete' and resource 'memory by key' are specific.
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?
The description explicitly tells when to use the tool: when context is stale, the task is done, or to clear sensitive data, providing clear context. It also recommends pairing with 'remember' and 'recall', guiding the agent on appropriate usage relative to siblings.
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 tool set includes both OpenReview-specific tools (e.g., get_paper, list_submissions) and a large number of unrelated tools for Pipeworx, Polymarket, and SEC filings. While individual descriptions are clear, the mix of domains creates confusion about which tools to use for a given task, leading to potential misselection.
Tool names follow inconsistent patterns: some use underscore_case (ai_visibility_check, generate_llms_txt), some are verb_noun (get_paper, list_venues), and others use descriptive phrases (ask_pipeworx_grounded, polymarket_arbitrage). The lack of a unified naming scheme makes the tool set feel disjointed.
With 37 tools, the count is too high for a server supposedly focused on OpenReview. Only about 6 tools are directly related to OpenReview; the rest are for unrelated domains like prediction markets, data retrieval, and memory management. The scope is unclear and overloaded.
For the OpenReview domain, the tool set covers basic retrieval (get_paper, search_notes, list_submissions) but lacks operations like creating or updating notes, which are common in a review platform. The inclusion of many non-OpenReview tools does not compensate for these gaps, leaving the surface incomplete for its stated purpose.