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 destructive and idempotent behavior. The description adds context about the purpose of deletion (stale context, sensitive data) and positions it as a cleanup action, which goes beyond the raw annotation flags.
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 core action, followed by concise usage context. Every word earns its place; no redundancy or filler.
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 one-parameter destructive tool with rich annotations (destructive, idempotent) and no output schema, the description fully covers purpose, usage, and behavioral context. Nothing essential is missing.
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 for the single 'key' parameter is complete (100% coverage), and the description simply restates 'by key' without additional semantic value. Baseline of 3 applies because schema covers all needed information.
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 the tool deletes a previously stored memory by key, using a specific verb and resource. It distinguishes itself from siblings like remember and recall by explicitly contrasting store, retrieve, and delete.
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 clear guidance on when to use: when context is stale, task is done, or sensitive data needs clearing. It also suggests pairing with remember and recall as alternatives, but lacks explicit 'when not to use' conditions.
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.
The tool set mixes general-purpose Pipeworx tools (ask_pipeworx, ai_visibility_check, bet_research) with only three paleontology-specific tools (find_fossils, get_taxon, list_subtaxa). Multiple similar 'ask_pipeworx' variants further blur distinctions, making it difficult for an agent to select the right tool without deep domain knowledge.
Tool names are mostly in snake_case and somewhat descriptive, but the naming conventions vary widely: imperative verbs (find_fossils), interrogative (suggest_questions), and nouns (recent_alerts). The presence of multiple 'ask_pipeworx' variants with inconsistent suffixes (beta, grounded) adds confusion.
With 34 tools, the server is oversized for its claimed paleontology focus. The vast majority of tools are unrelated to Paleobiology, making the server feel more like a general-purpose data API than a specialized paleontology tool. A focused server should have a smaller, targeted set.
For the Paleobiology Database purpose, the coverage is severely lacking: only three tools are directly relevant (find_fossils, get_taxon, list_subtaxa). Missing essential operations like searching taxa by name, retrieving occurrences by location, or accessing collections data. The tool set is not a coherent interface for the domain.