Skip to main content
Glama

watch_meal

Authorizes one automatic purchase of a specified sold-out dish when available, polling about every 20 seconds within your max price and expiry; no substitutions.

Instructions

Explicitly authorize ONE future automatic burza purchase of this exact sold-out dish. Copy section/number/name from menu. Expiry must contain timezone and be within 14 days. Polls about every 20 seconds, not instant; never substitutes another dish or exceeds max_price.

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": {
      "canteen": "<canteen>",
      "day": "<day>",
      "section": "<section>",
      "number": "<number>",
      "name": "<name>",
      "max_price": "<max_price>",
      "expires_at": "<expires_at>"
    },
    "name": "watch_meal"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes
nameYes
numberYes
canteenYes
sectionYes
confirmedNo
max_priceYes
expires_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses important traits: polling about every 20 seconds rather than instant, no substitution of another dish, no purchase above `max_price`, and a 14-day timezone-aware expiry. It omits what happens on cancellation and does not explain the optional `confirmed` flag, leaving some significant behavior unstated.

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

Conciseness5/5

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

The purpose is front-loaded in the first sentence, followed by actionable constraints with no filler. Every sentence contributes either routing, parameter sourcing, or behavioral expectation.

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?

This is a complex 8-parameter authorization tool with no annotations, 0% schema description coverage, and no output schema. The description covers the core purpose and several key constraints, but it does not explain all parameters or describe what the tool returns after creating the watch, so it is only partially complete.

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

Parameters3/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. It adds useful meaning for `section`, `number`, and `name` by saying to copy them from the menu, and explains `expires_at` constraints and `max_price`, but it leaves `canteen`, `day`, and `confirmed` unexplained.

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

Purpose5/5

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

The description gives a specific action and scope: 'authorize ONE future automatic burza purchase of this exact sold-out dish.' It clearly distinguishes this from an immediate `buy_meal` by emphasizing future, automatic, exact-dish, sold-out behavior.

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

Usage Guidelines4/5

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

The phrase 'sold-out dish' and 'future automatic' establish the usage context, and the description instructs how to source fields: 'Copy section/number/name from menu.' It does not explicitly name when to use `cancel_watch` or `list_watches`, nor does it state when not to use this tool, so it falls short of full alternative routing.

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