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 declare destructiveHint=true and idempotentHint=true, so the description's disclosure adds limited value. The description confirms deletion but does not elaborate on side effects or reversibility.
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, and includes usage guidance. No extraneous words.
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, full schema coverage, and sufficient annotations, the description covers purpose, usage context, and relationship with siblings. No gaps.
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 clear description of the 'key' parameter. The description adds no new semantic information 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' with a specific verb and resource, and distinguishes from siblings 'remember' and 'recall'.
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 when-to-use scenarios: 'context is stale, the task is done, or you want to clear sensitive data'. Lacks explicit when-not-to-use but is sufficient for a simple tool.
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.
While many tools have detailed descriptions that help differentiate them, there is significant overlap among query tools like ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research. The prediction market tools also cluster together, making it challenging for an agent to quickly pick the right one without careful reading.
Most tools follow a descriptive snake_case convention (e.g., ask_pipeworx, entity_profile, compare_entities). Minor deviations exist, such as 'ai_visibility_check' and 'deep_research', but overall the naming pattern is predictable and clear.
With 33 tools, the server is larger than typical single-domain servers. While it supports a broad data platform, this count feels somewhat bloated and could benefit from consolidation, especially among overlapping query tools.
The server is named 'Materials' but contains only two materials-specific tools (materials_search, materials_stability). The remaining 31 tools cover unrelated domains (finance, economics, prediction markets, etc.), leaving the stated domain severely incomplete.