Skip to main content
Glama

CarlNotes

Delete a tasting note

delete_note
DestructiveIdempotent

Delete a CarlNotes tasting note with its comments, if you wrote it. A note cannot be brought back. Use it when the user asks Carl or CarlNotes to delete my note or remove this note.

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": {
      "note_id": "<note_id>"
    },
    "name": "delete_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's added value is the irreversibility warning ('A note cannot be brought back'), the cascading deletion of comments, and the authorship precondition. It does not say what happens when the caller is not the author (error vs. no-op) or that repeated calls are harmless, though idempotentHint covers the latter.

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 short sentences, front-loaded with the destructive fact and cascade scope before the usage trigger. The enumerated trigger phrases ('delete my note or remove this note') are slightly redundant but serve intent matching, so the length is justified.

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

Completeness3/5

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

Safety context is well covered by the annotations plus the irreversibility and ownership statements, which is most of what matters for a one-parameter destructive tool. The gaps are the note_id source and the failure mode when the caller is not the author, both left unresolved across schema and description.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, so the description carries the full burden — yet it never explains what note_id is or where an agent should obtain it (presumably from read_notes). For a destructive operation, that omission forces guessing about identifier provenance.

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?

States a specific verb and resource ('Delete a CarlNotes tasting note'), and adds two scoping facts an agent could not infer from the name: comments go with it, and only notes you authored qualify. This clearly separates it from the read/save note siblings.

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?

Provides an explicit invocation trigger mapped to user phrasing ('delete my note', 'remove this note'), which is unusually actionable for intent routing. It stops short of stating when NOT to use it or naming an alternative for notes the user did not author.

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.