Skip to main content
Glama
Sign In
mealie-mcp

mealie-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete a recipe comment

delete_recipe_comment
DestructiveIdempotent

Delete a recipe comment by providing its ID. Requires a confirmation token from the first call to complete deletion.

Instructions

Deletes a comment. Requires confirmation: call once to receive a token, then again with that token.

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": {
      "comment_id": "<comment_id>"
    },
    "name": "delete_recipe_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
comment_idYesComment UUID, from list_recipe_comments
confirm_tokenNoConfirmation token from a previous call of this tool with the same arguments. Omit on the first call.

Output Schema

NameRequiredDescriptionDefault
truncatedNoPresent only when entries were dropped to fit the budget.
deleted_comment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token / maxLength
      Added value: +512
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "properties": {
+    "deleted_comment_id": {
+      "type": "string"
+    },
+    "truncated": {
+      "additionalProperties": true,
+      "description": "Present only when entries were dropped to fit the budget.",
+      "properties": {
+        "follow_up": {
+          "type": "string"
+        },
+        "reason": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "reason",
+        "follow_up"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "deleted_comment_id"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

The description adds the confirmation-token workflow, which is not fully captured by the annotations. The destructiveHint and readOnlyHint already signal safety profile, so the extra disclosure about the two-step process is useful but not exhaustive.

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 concise sentences lead with the action and then explain the confirmation requirement without extraneous detail. The structure is highly scannable and front-loaded.

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?

The description covers the necessary workflow and parameter origins, and an output schema exists to provide return details. It doesn't mention irreversibility, but the destructiveHint annotation covers that, so the tool is adequately specified.

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?

The schema descriptions already cover both parameters, including how to obtain comment_id and that confirm_token should be omitted on first call. The description does not add significant semantic meaning beyond repeating the confirmation flow, so baseline 3 applies.

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?

Description states 'Deletes a comment' with a specific verb and resource, making the core action unambiguous. It also highlights the two-step confirmation requirement, which clearly differentiates it from other delete tools.

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 explicitly instructs to call once to receive a token and then again with that token, providing necessary usage steps. It doesn't explicitly contrast with sibling delete tools, but the comment-specific scope is clear enough.

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

Deploy Server

Other Tools