Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx

list_households_webhooks

Retrieve a paginated list of household webhooks with configurable sorting and filtering options.

Instructions

Get All

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
orderByNo
perPageNo
queryFilterNo
orderDirectionNo
paginationSeedNo
accept-languageNo
orderByNullPositionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

With no annotations, the description must convey behavioral traits. 'Get All' incorrectly implies no pagination, but the schema includes pagination parameters. No disclosure of ordering, filtering, 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.

Conciseness2/5

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

While short, the description is severely under-specified, sacrificing necessary detail for brevity. Every sentence should add value; this one does not.

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?

Given the complexity of 8 optional parameters and an output schema, the description fails to mention pagination, filtering, or sorting. It is completely inadequate for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no information about any of the 8 parameters (page, orderBy, perPage, etc.), leaving the agent without guidance on their purpose or usage.

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

Purpose2/5

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

The description 'Get All' is a tautology that adds nothing beyond the tool name 'list_households_webhooks'. It fails to distinguish this tool from sibling listing tools like list_households_cookbooks or list_households_shopping_items.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/djwmarcx/better-mealie-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server