create_admin_backupsCreates admin backups of Mealie data, protecting recipes, meal plans, shopping lists, and household settings. Use it to restore or migrate your server.
Create One
| Name | Required | Description | Default |
|---|---|---|---|
| accept-language | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.20.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of disclosing behavior. 'Create One' only vaguely implies a creation operation and provides no detail about side effects, permissions, persistence, or consequences, adding no meaningful behavioral context beyond the tool name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short, but this is under-specification rather than effective conciseness. It does not front-load any useful information and every word fails to add meaning beyond the tool title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the ambiguous name and the complex set of admin backup siblings, this description is completely inadequate. Even with an output schema present, the agent has no idea what operation is performed, what the optional header affects, or how this tool relates to backup upload, restore, list, or delete operations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There is one optional parameter, accept-language, with 0% schema description coverage, and the description does not mention it or any other input. The description fails to compensate for the schema's lack of parameter explanation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is only 'Create One' and does not name the resource being created; an agent cannot tell from the text that this creates an admin backup. It also does nothing to distinguish the tool from the many other create_* siblings such as create_admin_backups_upload or create_admin_backups_by_file_name_restore.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use this tool versus alternatives. The description does not explain any scenario, prerequisite, or exclusion, leaving the agent to infer usage solely from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.