Skip to main content
Glama
Better Mealie MCP

Better Mealie MCP

List Households Mealplans Ical

list_households_mealplans_ical

Returns the token for the household's meal plan iCal feed, or null if the feed is disabled

Instructions

Returns the token for the household's meal plan iCal feed, or null if the feed is disabled

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_households_mealplans_ical"
  }
}

Input Schema

NameRequiredDescriptionDefault
accept-languageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.29.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the null-when-disabled outcome, which is genuine value, but it does not say whether this is read-only, whether calling it creates/enables a feed, or what permissions are required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single front-loaded sentence with zero waste that puts the return contract first. It is appropriately sized for a simple read tool, though very terse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-param read tool with an output schema, the description covers the core purpose and the null case. It still leaves gaps around the read-only nature and how it relates to the sibling create/delete/get_by_token iCal tools.

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

Parameters2/5

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

The sole parameter (accept-language) has 0% schema description coverage and the description does not mention it at all, so an agent gets no semantic help for the one input. The description does explain the return value (token or null), but an output schema already exists, reducing that value.

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

Purpose4/5

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

The description states specifically that it returns the iCal feed token for the household's meal plan, with a defined null case when the feed is disabled. That is a concrete verb+resource with a clear output contract. It does not distinguish itself from the sibling create_/delete_/get_by_token iCal tools, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus create_households_mealplans_ical, delete_households_mealplans_ical, or get_households_mealplans_ical_by_token. The description implies a read of the current feed token but never states preconditions or exclusions.

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

Deploy Server

Other Tools