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. The description adds that it deletes a memory, which is consistent. No additional behavioral details beyond the annotations are provided.
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 concise sentences that are front-loaded with the action and purpose. No extraneous information; 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, full schema coverage, and informative annotations, the description provides sufficient context: purpose, usage, and related tools. No output schema is needed.
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 'key' parameter fully defined. The description mentions 'by key' but adds no new semantic information beyond what the schema already 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 explicitly uses the verb 'Delete' and specifies the resource 'previously stored memory by key'. It clearly distinguishes from sibling tools 'remember' and 'recall' by naming them and implying different actions.
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?
Description provides explicit contexts: 'when context is stale, the task is done, or you want to clear sensitive data'. It also suggests pairing with related tools. However, it lacks explicit 'when not to use' guidance.
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.
Several clusters of tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all route/discover questions across the same 5,743 tools, differing mainly in mode or betaness. The polymarket_* family (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) similarly overlaps in prediction-market edge detection. An agent would frequently struggle to pick the right tool from these near-duplicate groups despite verbose descriptions.
Snake_case is used throughout, but patterns are mixed: some tools are verb-first (ask_pipeworx, find_sites, recall, forget, subscribe), some are noun phrases (current_conditions, entity_profile, bet_research), and some use a domain prefix (pipeworx_*, polymarket_*). The version-suffixed ask_pipeworx_beta is also a minor deviation from the otherwise clear descriptive style.
34 tools is excessive for a server named 'Usgs Water' since only 3 tools (current_conditions, daily_values, find_sites) actually relate to USGS water data. Even as a general Pipeworx platform server, the count is heavy, with many tools dedicated to niche prediction-market trading and meta-routing that inflate the surface.
Against the stated USGS Water purpose, the surface is severely incomplete: it lacks water-quality samples, groundwater data, site metadata details, historical statistics, rating curves, parameter code lookup, and flood/alert data. The remaining 31 tools cover an entirely different domain (SEC filings, drugs, prediction markets, npm scans, memory), so agents using this server for water data will hit dead ends almost immediately.