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 declare destructiveHint=true and idempotentHint=true, indicating a safe delete operation. The description confirms the destructive action ('Delete') and adds context about clearing sensitive data, but does not provide additional behavioral details beyond the 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 front-load the action and then provide usage guidance. No wasted words – every sentence adds value.
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 delete-by-key tool with full schema coverage and clear annotations, the description covers usage scenarios, pairing hints, and is complete enough. No output schema is needed for a deletion operation.
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 parameter 'key' described as 'Memory key to delete.' The description does not add extra semantics beyond what the schema provides, so baseline 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,' using a specific verb (delete) and resource (memory by key). It distinguishes from sibling tools by mentioning 'Pair with remember and recall,' making the purpose precise.
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 explicitly provides use cases: 'when context is stale, the task is done, or you want to clear sensitive data.' It also suggests pairing with remember and recall, offering alternatives and 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.
Most tools have distinct purposes within their own clusters, and the GSC tools are clearly separated. However, ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, and the several Polymarket tools (arbitrage, edges, fill_risk, kalshi_spread) can be confused without reading each description closely.
Names are broadly snake_case and readable, with some useful prefixes (gsc_, polymarket_, pipeworx_). But conventions are mixed: some are verb_noun (list_subscriptions, resolve_entity), some are noun_compound (bet_research, entity_profile), and some are bare verbs (forget, recall), which prevents a predictable pattern.
35 tools is heavy for any single server, but it is especially problematic given the server is named Google_search_console while only 4 of the 35 tools actually relate to Search Console. The rest form a sprawling Pipeworx/Polymarket research toolkit that would be far more coherent as its own server.
Relative to the stated Google Search Console purpose, the set is missing common operations such as submitting/removing sitemaps, requesting indexing, or managing URL inspections. The unrelated Pipeworx tools are extensive in their own domains but do not fill these gaps, leaving the GSC surface incomplete.