Skip to main content
Glama

diner_remember

DestructiveIdempotent

Explicitly save, replace or forget this account's private diner memory. Notes must contain 1–500 Unicode characters, including emoji; the service enforces this limit. Requires separate diner_write consent, not implied by read. Use expectedRevision from the account holder or diner_memory; ask before replacing their writing. Free; never orders anything. Returns acknowledgement only, never note contents. Deleting your note: This removes it from the diner’s current records. Older backups may still contain it, and restoring a backup could bring it back. Copies already shared with an AI agent, chat service or anyone else aren’t deleted here.

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": {
      "requestId": "<requestId>",
      "expectedRevision": "<expectedRevision>",
      "operation": "<operation>"
    },
    "name": "diner_remember"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo1–500 Unicode characters, including emoji. The service enforces 500 characters; the 1000 code-unit ceiling accommodates emoji.
seatNo
itemIdNo
operationYes
requestIdYes
expectedRevisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / note / description
      Added value: +"1–500 Unicode characters, including emoji. The service enforces 500 characters; the 1000 code-unit ceiling accommodates emoji."
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the destructiveHint and idempotentHint annotations, it discloses that deletion only affects current records while older backups and already-shared copies persist, that it returns acknowledgement only and never note contents, and that it is free and never orders anything. Those are exactly the behavioral facts an agent cannot derive from the structured fields.

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?

Purpose and consent requirements are front-loaded, and the deletion caveat is separated into its own labeled block. It is dense and runs long, but nearly every clause conveys operational information rather than filler.

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 correctly covers returns (acknowledgement only). Permissions, concurrency, and delete side effects are handled, though the multi-value operation enum is left unexplained for a six-parameter mutation tool.

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

Parameters3/5

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

Schema description coverage is only 17%, so the description must carry the load. It does explain expectedRevision's provenance and the 1-500 character service-enforced note limit, but the seven-value operation enum, the seat enum, itemId, and requestId get no meaning from the description.

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

Purpose5/5

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

The opening sentence names a specific verb set (save, replace, forget) against a specific resource (this account's private diner memory). It distinguishes the tool from diner_memory by contrasting write consent with read, so an agent can tell read from write without opening schemas.

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?

It states a hard prerequisite (separate diner_write consent, not implied by read) and a procedural rule (pull expectedRevision from the account holder or diner_memory, and ask before replacing their writing). It lacks an explicit 'don't use this for X, use sibling Y' exclusion, but the read/write split with diner_memory is implied clearly enough.

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