Retrieve all multi-purpose labels from your Mealie group. Use pagination, search, and filters to sort and find the labels you need.
Get All [GET /api/groups/labels]
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| search | No | ||
| orderBy | No | ||
| perPage | No | ||
| queryFilter | No | ||
| orderDirection | No | desc | |
| paginationSeed | No | ||
| orderByNullPosition | No |
Changes observed during successful MCP inspections.
v0.2.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description fails to disclose any behavioral traits like read-only nature, pagination, or potential side effects. Completely inadequate.
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?
Extremely brief but not effectively concise; it omits essential information. The format 'Get All [GET /api/groups/labels]' is a placeholder, not a useful description.
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?
With no annotations, no output schema, and no parameter explanation, the description is highly incomplete. It fails to provide necessary context for an agent to use this tool correctly.
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 coverage is 0% with 8 parameters, yet the description explains none of them. The agent gets no help understanding page, search, orderBy, etc. beyond what the schema minimally offers.
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?
Description 'Get All' only repeats the HTTP method and endpoint, giving no explicit clarification on what resource is being retrieved. While the name suggests labels, the description adds no value.
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 on when to use this tool versus its siblings (e.g., groups_multi_purpose_labels_get_one, create_one). The description lacks context for appropriate invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.