get_organizers_tools_slug_by_tool_slugFetches a specific organizer tool from Mealie using its slug and returns details such as name, ID, and attributes. Use it to resolve a slug into complete tool data for subsequent updates or recipe associations.
Get One By Slug
| Name | Required | Description | Default |
|---|---|---|---|
| tool_slug | Yes | ||
| 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 provided, the description carries the full burden of behavioral disclosure. It indicates a read operation via "Get" and a singular result via "One," but it says nothing about required permissions, not-found behavior, response shape, or side effects.
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 very short and front-loads its single idea with no filler. However, it is under-sized rather than well-structured: it is a fragment that omits the resource and useful context.
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?
For a tool with no annotations, 0% schema descriptions, and many sibling tools, four words are insufficient. The output schema removes the need to explain return values, but the description still leaves the resource identity, slug semantics, and behavioral expectations unclear.
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 needs to compensate. "By Slug" at least suggests tool_slug is the lookup identifier, but it gives no detail about slug format or constraints and provides no explanation of the accept-language parameter.
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 "Get One By Slug" is essentially a paraphrase of the tool name and title; it names neither the resource (organizers tools) nor what is actually returned. It provides a verb and a lookup key, but no concrete resource or differentiation from sibling tools like get_organizers_tools_by_item.
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 when-to-use or when-not-to-use guidance is provided, and no alternative tools are mentioned despite many sibling tools that also retrieve organizer tools. The only implied usage is that a slug is the lookup key, which is already visible in the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.