create_shared_recipesGenerate a shareable link for a Mealie recipe by providing its ID, with optional expiration date and language settings to control access duration and locale.
Create One
| Name | Required | Description | Default |
|---|---|---|---|
| recipeId | Yes | ||
| expiresAt | No | ||
| 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?
With no annotations, the description carries the full burden of disclosing behavior, side effects, and requirements. 'Create One' discloses nothing about what creating a shared recipe entails, such as visibility, expiry behavior, authentication needs, or whether the operation is immediate.
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?
Two words are under-specification rather than conciseness. There is no structured information, no front-loaded context, and no meaningful content for the agent to use.
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?
Even with an output schema present, the description leaves out basic context about what sharing means, how expiration works, and how this relates to other shared-recipe operations. The definition is effectively a placeholder and is inadequate for a tool with three parameters.
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?
Schema description coverage is 0%, so the description needed to explain the meaning of recipeId, expiresAt, and accept-language. It provides no semantic help whatsoever, leaving the agent to guess why expiresAt matters or how accept-language affects the request.
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 'Create One' is a fragment that does not name the resource being created or explain what a shared recipe is. It restates the create action implied by the name and title without adding any distinguishing information.
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?
No guidance is given about when to use this tool versus related tools such as list_shared_recipes, get_shared_recipes_by_item, or delete_shared_recipes_by_item. The intended use case and conditions for choosing this endpoint are entirely absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.