Skip to main content
Glama

Niche of One Network

Forget my reading data

forget_me
DestructiveIdempotent

Members. Clear the bookmarks, reading progress and interests this server keeps for you. Shows what it will clear first; call again with confirm true to clear.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "forget_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds the non-obvious dry-run-first behavior, which is genuinely valuable context beyond structured fields. It does not state whether clearing is reversible or how it interacts with other member data, leaving some gaps for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the action and its scope, followed by the confirm behavior. The opening "Members." fragment is the only genuinely wasted token.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still tells the agent what the preview step surfaces ("Shows what it will clear") and how to proceed. For a destructive one-parameter tool this is close to sufficient; reversibility and scope of "interests" remain unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter is undocumented there, so the description carries the burden. It does explain confirm's role via the two-step pattern, but never names the parameter explicitly or states its default behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ("Clear") with enumerated resources: bookmarks, reading progress, and interests. That level of detail distinguishes it from other member-data siblings, though the leading fragment "Members." is a dangling label that adds no meaning.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the two-step flow explicitly: call once to preview, then call again with confirm true to actually clear. It stops short of saying when to prefer this over sibling tools like reader_export_notes or my_account, but the call pattern itself is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources