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.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true. Description aligns with this and adds context about clearing stale or sensitive data, which enhances transparency without contradicting 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, no wasted words. Purpose is front-loaded. Every sentence is informative and earns its place.
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?
Given the tool's simplicity (one param, no output schema, annotations present), the description covers key usage and purpose. Slight gap: no mention of return value or error behavior, but acceptable for a low-complexity tool.
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 description coverage is 100% for the single parameter 'key'. The description only says 'by key', adding no new semantics beyond the schema. Baseline 3 per guidelines.
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', identifying the action (delete) and the resource (memory by key). It distinguishes from siblings like 'remember' and 'recall' by mentioning them.
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?
Explicit when-to-use guidance is provided: 'Use when context is stale, the task is done, or you want to clear sensitive data...' and it suggests pairing with related tools '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.
Many tools have overlapping purposes, especially the query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim) and prediction market tools (bet_research, polymarket_arbitrage, polymarket_edges). The Sefaria-specific tools are few, making it hard to distinguish between the core functionality and auxiliary utilities.
Tool names follow inconsistent conventions: some use verb_noun (ask_pipeworx, get_text), some noun_verb (ai_visibility_check, bet_research), and some are standalone names (pipeworx_feedback, polymarket_edges). This mix of patterns makes the set appear haphazard.
With 33 tools, the server is heavily overloaded, especially given the name 'Sefaria' which implies a focused set for Jewish text access. The vast majority of tools are unrelated to Sefaria, belonging to the Pipeworx ecosystem, making the count inappropriate for the server's stated purpose.
For a server named Sefaria, the tool surface is severely incomplete. Only three tools (get_text, get_commentaries, lookup_ref) directly relate to Jewish texts, missing fundamental operations like search, list books, or manage content. The remaining 30 tools belong to other domains, leaving the core domain under-served.