Skip to main content
Glama

meal_history

Retrieve consumed meals and account transactions from your canteen history, optionally filtered by date range; pending orders are excluded.

Instructions

Consumed meals/transactions from account history (default last year); pending orders are separate.

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": "meal_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNo
untilNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it discloses the important default time window (last year) and that only consumed/settled transactions are returned, which is genuine behavioral context. It says nothing about result ordering, volume, or pagination limits for what could be a year of history.

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 tight sentence with the core scope front-loaded and the sibling disambiguation trailing. No filler, though the parenthetical phrasing is slightly cryptic.

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?

An output schema exists, so return values need not be explained, and the default window is covered. However, with no annotations and two undocumented date parameters, an agent still lacks the date format and result-size expectations needed to call this confidently over a long history.

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 coverage is 0% – `since` and `until` have only titles and a string/null anyOf, with no format, timezone, or inclusivity guidance. The description only indirectly touches `since` via the 'default last year' note and adds nothing about `until` or the expected date string format.

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 a specific resource (consumed meals/transactions from account history) and scopes it clearly. It also explicitly separates itself from pending orders, which maps to the sibling `orders` tool, so the agent can distinguish them.

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 parenthetical '(default last year)' and 'pending orders are separate' imply when to reach for this tool versus `orders`, but no alternative is named explicitly and no conditions for choosing `meal_statistics` or `orders` are stated. Usage is inferable rather than prescribed.

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