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 provide destructiveHint=true and idempotentHint=true. Description adds 'clear sensitive data' context but doesn't discuss edge cases like missing key or required permissions.
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, no wasted words. First sentence defines purpose, second provides usage guidance. Efficient and front-loaded.
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 annotations and no output schema, the description covers purpose, usage, and pairing. Lacks detail on error behavior but adequate for basic use.
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 parameter 'key' described as 'Memory key to delete'. Description reinforces 'by key' but adds no new semantic detail beyond schema.
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?
Description clearly states 'delete a previously stored memory by key' with a specific verb and resource. It distinguishes from sibling tools by mentioning 'pair with remember and recall', making the role as delete counterpart explicit.
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 explicit use cases: when context is stale, task done, or to clear sensitive data. Lacks explicit alternatives or when-not-to-use, but pairing mention gives context.
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 tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all accept natural-language factual questions, and ask_pipeworx_beta is explicitly described as currently identical to ask_pipeworx. The entity tools (entity_profile, compare_entities, recent_changes, resolve_entity) and the many Polymarket tools also blur together, making misselection likely.
Most names are snake_case and readable, with recognizable prefixes like cta_, polymarket_, and ask_pipeworx_. However, conventions are mixed: bare verbs (remember, forget, subscribe), noun-style phrases (entity_profile, bet_research), and variants like ai_visibility_check vs scan_competitor_ai_presence prevent a single predictable pattern.
35 tools is above the comfortable range, and the count is especially mismatched for a server named 'Cta': only 4 tools actually concern Chicago transit, while the other 31 form a general-purpose research, prediction-market, and memory suite. The set feels like multiple unrelated servers merged together.
As a CTA server, the surface is notably incomplete: it has bus/train positions and predictions but lacks alerts, service disruptions, route listings, and station/stop metadata. The broader Pipeworx tools are extensive but appear bolted on, so the overall set has no coherent domain against which completeness can be judged.