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 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint and idempotentHint. The description adds specific context: it deletes a previously stored memory by key, and explains use cases like clearing sensitive data. This goes beyond the raw hints by specifying what is affected.
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?
The description is two sentences, front-loaded with the action, and every clause adds value: the operation, use cases, and related tools. No wasted 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 one-parameter tool with no output schema, the description covers purpose, usage timing, and relationships to sibling tools. Combined with the annotations, it is complete for effective agent invocation.
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?
The input schema provides 100% coverage with a clear description for the 'key' parameter ('Memory key to delete'). The description adds no additional parameter meaning beyond the schema, so the baseline score of 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 states a specific verb and resource: 'Delete a previously stored memory by key.' It clearly distinguishes itself from sibling tools by naming the action (delete) and the complementary tools '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?
The description provides explicit conditions for use: 'when context is stale, the task is done, or you want to clear sensitive data.' It also mentions pairing with 'remember' and 'recall,' which implies alternatives, although it does not explicitly state when not to use this 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.
Most tools have distinct purposes, but there is some overlap among ask_pipeworx, ask_pipeworx_grounded, and deep_research, all of which query the Pipeworx database with different levels of structure. The detailed descriptions help differentiate them, but the overlap is notable.
All tool names use snake_case consistently, which is good. However, the naming conventions vary: some are descriptive phrases (e.g., ai_visibility_check), others are verb_noun (e.g., list_subscriptions), and some are compound nouns (e.g., entity_profile). Lack of a single pattern reduces consistency slightly.
34 tools is on the higher side for a single server, but it may be justified given the broad scope of Pipeworx data sources. However, the server name 'Mast Nasa' implies a focus on astronomy, yet only a few tools relate to that domain, making the count feel inflated and unfocused.
The tool set is comprehensive for the Pipeworx data platform, covering querying, grounding, entity resolution, comparison, subscriptions, and more. However, for the implied NASA/Mast domain, the surface is severely incomplete with only four astronomy-specific tools, leaving obvious gaps.