Skip to main content
Glama

Food for a day

trainrec_food_day
Read-only

Everything eaten on one day, each entry with its id and version, totals by meal and for the day, and what is left of the targets.

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

Input Schema

NameRequiredDescriptionDefault
dayNoYYYY-MM-DD. Default today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, openWorldHint=false, so safety is covered and the bar is lower. The description does add useful behavioral content beyond them: it discloses the return shape (entries with id and version, meal totals, day totals, remaining targets), which matters because there is no output schema. It says nothing about pagination, missing days, or what happens when no entries exist.

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, front-loaded with the main object ('everything eaten on one day') and then enumerating the return payload. Every clause carries information; nothing is repeated or wasted.

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 low-complexity, single-optional-parameter read tool with no output schema, the definition covers what the tool returns in enough detail to call it correctly. The remaining gap is modest: empty-day behavior and result size are 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?

There is one optional parameter and schema description coverage is 100%, with the schema already documenting the YYYY-MM-DD format and the 'default today' behavior. The description reinforces the one-day granularity but adds no format or edge-case detail beyond the schema, 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?

Names a specific resource and scope: everything eaten on one day, plus per-meal and per-day totals and remaining targets. That is far more concrete than a tautology, and it is plainly a read of the food diary rather than a mutation, so it separates itself from edit/log/delete siblings. It stops short of naming a sibling it could be confused with (e.g. an overview tool), which keeps it at 4.

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: 'everything eaten on one day' tells the agent this is the day-level food lookup, and the default of 'today' suggests the common case. There is no explicit when-to-use/when-not guidance and no pointer to the overview or measurement siblings for cross-domain questions, so the agent must infer the boundary.

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