Skip to main content
Glama

Forget a style preference

forget

Deletes one saved style note by its id (ids are in get_profile). Use when the member says a preference no longer applies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that this is a destructive mutation and limits the blast radius to "one" note. It says nothing about permanence, confirmation, permissions, or what happens when the id is unknown.

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

Conciseness5/5

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

Two short clauses: what it does and when to use it. The action is front-loaded and nothing is wasted. The pointer to `get_profile` is folded inline instead of becoming a separate sentence.

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?

For a one-parameter, non-annotated delete with no output schema, the definition covers the essentials: the action, the id source, the single-note limit, and the triggering situation. It still leaves open how failure or duplicate deletion behaves, which matters for a destructive call.

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 description coverage is 0%, so the description must compensate, and it does: it tells the agent the single parameter is an id and that valid ids come from `get_profile`. It also implies one id per call. No format details (for example, a prefix or UUID shape) are given, which keeps this from a 5.

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?

Specific verb and resource: "Deletes one saved style note by its id." It is clearly distinguishable from the add-a-preference counterpart implied by the sibling `remember`. It does not name a sibling explicitly for contrast, but the scope (single style note, deleted by id) is unambiguous.

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?

Gives a concrete trigger condition: "Use when the member says a preference no longer applies." That is a clear usage context rather than implied guidance. It stops short of exclusions or naming the alternative path (for example, updating a preference instead of deleting it).

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