Skip to main content
Glama

metri: Calorie & Macro Tracker

Today's full breakdown

metri_today_details
Read-onlyIdempotent

App-only companion to metri_show_today: the full day grouped by eating event, with per-item macros and the batch component breakdown, used by the metri card's fullscreen view. day and summaryDays are dates as YYYY-MM-DD, counted in the account's time zone like the card's own day. Pass summaryDays to also get back the calorie and macro totals plus the goal in force for each of those days, which colour the day strip in that same view. Do not call this to answer the user in chat; use metri_get_diary instead.

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": {
      "day": "<day>"
    },
    "name": "metri_today_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes
summaryDaysNo

Output Schema

NameRequiredDescriptionDefault
daysNo
goalYes
itemsYes
mealsYes
totalsYes
componentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior: it is an app-only presentation view, and day/summaryDays are interpreted in the account's time zone like the card's own day — a non-obvious semantic. It does not discuss limits on how many summaryDays are accepted.

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 positioning, then parameter semantics, then the exclusion rule — a sensible order. Some clauses, like 'which colour the day strip in that same view', are decorative UI detail rather than actionable information.

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 full annotations and an output schema, the definition covers identity, time-zone semantics, param formats, and the chat-vs-app boundary. Only the exact interaction between day and summaryDays remains underspecified.

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?

With 0% schema coverage the description must carry the load, and it does: both params are dated as YYYY-MM-DD in the account time zone, and summaryDays is explained as adding calorie/macro totals plus the goal in force for each listed day. It leaves slight ambiguity about whether day must also appear in summaryDays, but compensates well for an undocumented schema.

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 names a precise retrieval scope — the full day grouped by eating event with per-item macros and batch component breakdown — and positions it explicitly against both metri_show_today (companion) and metri_get_diary (the chat-facing alternative). An agent can distinguish it from siblings without opening schemas.

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

Usage Guidelines5/5

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

It states a hard when-not rule ('Do not call this to answer the user in chat') and names the replacement (metri_get_diary), plus implied usage for the card's fullscreen view. Both the allowed context and the excluded context are explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources