Skip to main content
Glama
Better Mealie MCP

Better Mealie MCP

Patch Recipes By Slug Last Made

patch_recipes_by_slug_last_made

Update a recipe's last-made timestamp by slug to keep preparation history accurate and track when each dish was cooked.

Instructions

Update a recipe's last made timestamp

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": {
      "slug": "<slug>",
      "timestamp": "<timestamp>"
    },
    "name": "patch_recipes_by_slug_last_made"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
timestampYes
accept-languageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.31.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observedv3.20.1

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses almost nothing: no mention of overwrite semantics, whether the timestamp must be in the past, idempotency, or required scopes/auth. 'Update' implies mutation but nothing about reversibility or side effects is given.

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?

A single short sentence with no filler and the key detail (which field) front-loaded. It is efficient rather than padded, but it is also too thin to be called well-structured.

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

Completeness2/5

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

For a mutation tool with zero annotations and fully undocumented parameters, the description explains far too little; the output schema does relieve it of explaining return values, but that is the only thing covered. An agent could invoke it but could easily misuse the timestamp or ignore accept-language.

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% across 3 parameters, and the description only obliquely covers 'timestamp' via 'last made timestamp'. The required 'slug' identifier and the optional 'accept-language' parameter receive no explanation anywhere, so an agent gets no help on what accept-language influences or what format slug takes.

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?

The description states a specific verb and resource plus the exact field being changed ('Update a recipe's last made timestamp'), which distinguishes it from a general patch_recipes_by_slug in substance. It stops short of naming or contrasting any sibling directly, so an agent must infer the difference from the field name alone.

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

Usage Guidelines2/5

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

There is no statement of when to use this narrow field-patch versus patch_recipes_by_slug or update_recipes_by_slug, and no prerequisites or exclusions. The only implicit guidance comes from the field name in the sentence.

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