Skip to main content
Glama
Sign In
mcp-mealie

mcp-mealie

by obrien-matthew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_label

Update a label's name or color by providing its ID and the desired values.

Instructions

Patch a label.

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": {
      "label_id": "<label_id>"
    },
    "name": "update_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
label_idYes
nameNo
colorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

D1.6/5.0
Behavior2/5

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

The word 'Patch' implies partial update, but no further details are given. Without annotations, the description fails to disclose error conditions, permission requirements, or effects of omitting optional fields.

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

Conciseness2/5

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

Three words is extremely concise but at the cost of utility. There is no structure or front-loading of critical information.

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

Completeness1/5

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

Completely inadequate for a tool with no output schema, no annotations, and three parameters. The description offers no insight into return values, side effects, or dependencies.

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

Parameters1/5

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

The description adds no meaning to the three parameters (label_id, name, color). With 0% schema description coverage, the agent receives no additional insight into parameter formats or semantics.

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

Purpose2/5

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

The description 'Patch a label.' is a tautology, restating the tool's purpose without specificity. It does not distinguish from sibling tools like update_category or update_food.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., create_label, get_label). There is no mention of prerequisites or context.

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