Skip to main content
Glama
supvan-e11

supvan-e11

by marco308

preview_freezer_label

Generate a freezer label preview with dish name and freeze date, plus optional use-by date, portions, and QR code; returns a preview_id for printing the label.

Instructions

Picture of a freezer label, and a preview_id to print it with print_label: dish name large, then the date it was frozen. frozen defaults to today; use_by and portions are added only when given (ISO dates, e.g. 2026-10-01). qr: optional text/URL for a QR code at the left end.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dish": "<dish>"
    },
    "name": "preview_freezer_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrNo
dishYes
frozenNo
use_byNo
portionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does reasonably well: it discloses the returned preview_id, the label layout order (dish name large, then frozen date), the default for frozen, the conditional inclusion of use_by/portions, and QR placement. It still does not say whether anything is persisted or how long a preview_id remains valid.

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?

Front-loaded with purpose and return value, then parameter behavior, with no filler. The colon-and-fragment structure ('print_label: dish name large...') is dense but readable.

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

Completeness4/5

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

Five parameters with zero schema descriptions are all addressed, and the return value is explained despite there being no output schema. For a read-only rendering tool the remaining gaps (preview lifetime, whether images are stored) are minor.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does: frozen defaults to today, use_by and portions are applied only when supplied, ISO date format is given with an example, and qr is described as optional text/URL rendered at the left end. Only dish's formatting beyond 'large' and portions' expected range are unstated.

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?

Names the artifact produced (a freezer label picture) and the return value (preview_id), and ties it to the sibling print_label, so an agent can tell this is the preview half of a two-step workflow. The phrasing 'Picture of a freezer label' is slightly awkward as an action statement but unambiguous.

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

Usage Guidelines3/5

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

The workflow is implied by 'print it with print_label', which tells the agent this is a non-printing preview step. It never states when to prefer this over the sibling preview_label, nor any exclusion such as 'do not use this to actually print'.

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