Skip to main content
Glama
mijneetmeter-mcp

mijneetmeter-mcp

by jhofstede

get_diary

Read-only

Retrieve diary entries for a specific date and meal to review what was logged for breakfast, lunch, dinner, or snacks.

Instructions

Read the diary entries for one date and meal moment.

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": {
      "date": "<date>",
      "meal": "<meal>"
    },
    "name": "get_diary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate in DD-MM-YYYY format
mealYesMeal moment: ontbijt/breakfast, lunch, avondeten/dinner, tussendoor/snack

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile needs no restating. The description contributes the scoping detail that results are limited to a single date and meal, but says nothing about what happens when no entries exist or how results are ordered. Against annotation coverage, a 3 is appropriate.

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?

A single sentence with the scope constraint front-loaded and no filler whatsoever. Nothing in it could be removed without losing meaning.

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?

For a two-parameter read tool with annotated safety profile and fully described schema parameters, the definition covers what an agent needs to call it correctly. The only real gap is differentiation from the whole-day sibling, which is a small omission for a tool of this simplicity.

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 100%: the date format (DD-MM-YYYY) and the meal aliases (ontbijt/breakfast, lunch, avondeten/dinner, tussendoor/snack) are fully documented in the schema. The description only restates the concept of a date and a meal moment, adding no format or aliasing detail beyond the structured data, so the baseline 3 applies.

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 gives a specific verb ('Read') and resource ('diary entries') with an explicit scope: one date and one meal moment. It is clear what the tool returns, but it never distinguishes itself from the sibling get_diary_day, which an agent could easily confuse with a single-meal read.

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?

Usage is only implied by the 'one date and meal moment' phrasing — the agent can infer this is for narrow, single-meal lookups rather than whole-day retrieval. There is no explicit statement of when to prefer it over get_diary_day or today, and no mention of prerequisites or empty-result behavior.

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