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=true and idempotent=true. The description confirms deletion but adds little beyond the key detail already present in the schema. No contradictions.
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 with front-loaded purpose. Every sentence adds value with zero waste.
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 simple interface (one required param, no output schema), the description adequately covers purpose and usage. It also contextualizes with sibling tools.
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% and the description merely repeats 'by key'. No additional constraints or format guidance are provided, meeting the baseline for high coverage.
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', providing a specific verb and resource. It distinguishes itself from sibling tools 'remember' and 'recall' as the delete counterpart.
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 gives explicit usage scenarios ('when context is stale, task is done, or clear sensitive data') and advises pairing with siblings. While it doesn't explicitly state when not to use, the context is clear enough for an agent.
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 ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research cluster overlaps heavily on question-routing, and the six polymarket_* tools all operate on prediction-market edges and can be confused. The ipma_*, memory, and subscription tools are distinct, but the overlapping clusters create real misselection risk.
Snake_case is used throughout and there are clear prefix groups (ipma_*, ask_pipeworx, polymarket_*), but the rest mix verb-first (compare_entities, discover_tools), noun-first (entity_profile, bet_research), and bare verbs (remember, recall, forget). Readable overall, but no consistent verb_noun convention.
36 tools is heavy, and the server name 'Ipma Pt' implies a narrow Portugal-weather service while 31 of the tools belong to a broad Pipeworx data/prediction-market platform. The scope mismatch makes the count feel bloated rather than curated.
The dominant Pipeworx domain is well covered: querying, grounded answers, deep research, entity resolution, comparison, claim validation, subscriptions, memory, and tool discovery are all present with few dead ends. Minor gaps exist (e.g., no general web search tool, thin IPMA historical/warning coverage), but agents can work around them.