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 readOnlyHint=false, so the agent knows this is a destructive action. The description adds no new behavioral context beyond confirming deletion. With annotations present, a 3 is appropriate.
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 with no wasted words. Every sentence adds value: first states purpose, second gives usage context. Front-loaded clearly.
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 annotations covering safety, the description is complete. It states what it does, when to use it, and how it relates to siblings.
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% for the single parameter 'key', which is described as 'Memory key to delete' in the schema. The description does not add any additional detail about parameter format, constraints, or validation, so baseline 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 'Delete a previously stored memory by key.' It specifies the verb (delete), resource (memory), and scope (by key), and distinguishes from sibling tools 'remember' and 'recall' by pairing 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?
The description provides explicit usage scenarios: 'when context is stale, the task is done, or you want to clear sensitive data.' It also advises pairing with related tools but does not explicitly state when not to use it, though the positive guidance is strong.
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, such as multiple tools for querying Pipeworx data (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim) and numerous tools for AI news/tools (get_ai_news, get_ai_toolbelt, get_briefing, get_model_landscape, etc.). This will cause an agent to frequently misselect the appropriate tool.
Most tools follow a verb_noun pattern in snake_case (e.g., compare_entities, discover_tools, get_briefing). However, a few deviate like 'bet_research' (noun_verb) and 'what_happened' (phrase), but overall the pattern is largely consistent.
38 tools is excessive for a server called 'Ai Briefing', which suggests a focused purpose. The tool count spans multiple domains (AI visibility, Pipeworx queries, Polymarket betting, memory, subscriptions) making it feel overstuffed and unfocused.
The tool set covers many aspects of its broad domain (querying, comparing, subscribing, memory), but there are notable gaps: no tool for modifying subscriptions, no user profile management, and the AI news tools overlap rather than cover distinct needs.