Skip to main content
Glama
Better Mealie MCP

Better Mealie MCP

Create Organizers Categories

create_organizers_categories

Creates a new category in Mealie's database, letting you group recipes under custom labels and keep your collection organized.

Instructions

Creates a Category in the database

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

Input Schema

NameRequiredDescriptionDefault
nameYes
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.1/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the fact of a write: no permission requirements, no duplicate/conflict behavior, no side effects, no error semantics. One sentence restating the name is not enough for an unannotated mutation tool.

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

Conciseness3/5

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

It is a single front-loaded sentence with no wasted words, so structure is fine. The problem is under-specification rather than verbosity: the sentence stops far short of what an agent needs before invoking a write tool.

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?

A create/mutation tool with no annotations, no schema descriptions, and an unmentioned optional language parameter. The existence of an output schema relieves it of describing return values, but everything else an agent needs to call this safely and correctly is missing.

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 two parameters, and the description says nothing about either. The word "Category" weakly implies that the required "name" is the category name, but the format, uniqueness constraints, and the meaning of the optional "accept-language" header are entirely undocumented.

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

Purpose3/5

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

"Creates a Category in the database" gives a specific verb (Creates) and resource (Category), so the basic action is understandable. However, "in the database" adds nothing, and nothing distinguishes it from the sibling create_organizers_categories_merge or explains what a Category is in this system.

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 guidance on when to use this tool versus the merge variant or the update/get/list siblings. No prerequisites, no mention of what happens if the category already exists, and no conditions for choosing this over an alternative.

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