Skip to main content
Glama
mijneetmeter-mcp

mijneetmeter-mcp

by jhofstede

get_diary_day

Read-only

Retrieve all diary entries for a specified day, grouped into breakfast, lunch, dinner, and snacks, with product, amount, unit, and kcal details.

Instructions

Read the diary entries of a full day. Returns {ontbijt, lunch, avondeten, tussendoor}, each a list of entries with product, amount, unit and kcal.

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>"
    },
    "name": "get_diary_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate in DD-MM-YYYY format

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?

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description's main contribution is disclosing the return shape, which matters because there is no output schema. Naming the four meal buckets and per-entry fields (product, amount, unit, kcal) tells the agent exactly what a response contains, though it says nothing about behavior for days with no entries.

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?

Two sentences with zero filler: the action and scope come first, then the return shape. Every clause earns its place by conveying either purpose or output structure.

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 single-parameter read tool with no output schema, the description supplies the essential missing piece: the structure of the returned object. It is nearly complete, with only edge-case behavior (empty days, invalid date handling) left unstated.

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 100% and the single date parameter already documents the DD-MM-YYYY format, so the schema carries the parameter burden. The description adds no additional meaning about the date parameter (e.g., timezone handling or whether future dates are valid), which is the baseline 3 case.

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?

States a specific verb and resource: 'Read the diary entries of a full day,' including scope (one day) that separates it from a broader diary getter. It does not name or contrast with any sibling such as get_diary or today, so differentiation is implied rather than explicit.

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 implied by the day-scoped framing and the required date parameter, but there is no explicit when-to-use statement, no exclusion, and no pointer to the alternative tools an agent would weigh it against (get_diary, today, search_food).

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