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 useful context like deleting sensitive data and pairing with remember/recall, aligning with the annotations. No contradictions found.
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 the action, no wasted words. Every sentence adds meaningful information, making it highly concise and well-structured.
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 full schema coverage and annotations, the description fully covers purpose, usage context, and related tools. An output schema is not needed since return values are not described, but this is acceptable given the tool's simplicity.
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 the single parameter 'key' described as 'Memory key to delete'. The description's 'by key' matches but adds no additional meaning beyond the schema, so a baseline of 3 applies.
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 uses a specific verb ('Delete') and resource ('previously stored memory by key'), clearly differentiating it from siblings like remember and recall by explicitly pairing with them. It states exactly what the tool does.
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?
It clearly states when to use the tool ('when context is stale, the task is done, or you want to clear sensitive data'), providing concrete scenarios. It also mentions related tools (remember and recall) but does not explicitly state when not to use it, so it's a 4 rather than a 5.
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.
Multiple tools have unclear boundaries: ask_pipeworx and ask_pipeworx_beta are described as currently identical, and citation vs citations differ only by pluralization while actually accepting different ID types (OCI vs DOI). The server is named Opencitations but 31 of 37 tools serve unrelated purposes, so an agent cannot infer what the set is for without reading very long descriptions.
All names are snake_case and family prefixes (polymarket_*, ask_pipeworx_*, pipeworx_*) give some predictability. However, conventions are mixed: bare resource nouns (citation, citations, references, metadata) coexist with verb_noun tools (resolve_entity, validate_claim) and noun phrases (recent_changes, entity_profile, deep_research), so there is no single pattern that lets an agent predict tool names.
37 tools is well past the 25+ threshold for a heavy set, and most are redundant with the server's own router tools — ask_pipeworx already reaches 5,759 underlying tools, making many direct tools overlapping conveniences. The scope also wildly overshoots the server name: only 6 of 37 tools serve the Opencitations citation-graph domain.
For the named OpenCitations domain, the core citation-graph read operations exist (metadata, incoming citations, outgoing references, counts, OCI record lookup), but there is no paper/DOI discovery or search tool — an agent must already possess a DOI, a dead end for title/author queries. The broader accidental domain (data routing, company research, prediction markets, monitoring) is covered unusually well, but that does not serve the server's stated purpose.