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=true and idempotentHint=true. The description adds context about clearing sensitive data, which reinforces destructive nature but doesn't add significant new behavioral info beyond annotations.
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: first for purpose, second for usage guidelines. Front-loaded and efficient with no unnecessary 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?
Given the tool's simplicity (one param, no output schema), the description covers purpose and usage adequately. It could mention behavior when key doesn't exist, but idempotence is hinted.
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 single 'key' parameter described as 'Memory key to delete'. The description does not add extra meaning beyond what the schema provides, so baseline 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 clearly states 'Delete a previously stored memory by key' with a specific verb (delete) and resource (memory). It distinguishes from sibling tools like 'remember' and 'recall' by specifying the action of deletion.
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 scenarios for use: 'when context is stale, the task is done, or you want to clear sensitive data'. It also references pairing with 'remember' and 'recall', though it lacks explicit when-not instructions.
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 ask_pipeworx and ask_pipeworx_grounded overlap (one is grounded), and bet_research/validate_claim/compare_entities/entity_profile all query Pipeworx data with different intents, which could cause confusion.
Names are consistently lower_snake_case and mostly follow a verb_noun pattern (e.g., search_podcasts, get_podcast, list_subscriptions). A few compound names like pipeworx_feedback and polymarket_arbitrage deviate slightly but remain readable.
30 tools is excessive for a server named 'Podcastindex'. It aggregates unrelated domains (podcasts, Pipeworx queries, Polymarket, memory, etc.), making it feel like a kitchen sink rather than a focused tool set.
For podcasts, the tool set covers search, metadata, episodes, and trending but lacks subscription management. For the broader Pipeworx domain, ask_pipeworx and discover_tools provide wide access, but specific gaps exist (e.g., no direct SEC filing query). Overall, the surface is broad but uneven.