Skip to main content
Glama

get_nutrition_daily_settings

Read-only

Retrieve your nutrition goals and targets for a given date, including calorie and macronutrient targets plus plan configuration.

Instructions

Get nutrition plan/settings for a date

    Returns the user's nutrition goals and targets including
    calorie targets, macronutrient goals, and plan configuration.

    Args:
        date: Date in YYYY-MM-DD format
    

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_nutrition_daily_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 is covered structurally. The description adds real value by enumerating the returned content (goals, targets, macros, configuration), but says nothing about what happens when no plan is configured for that date or whether the response is per-user only.

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?

Purpose is front-loaded in the first line, followed by return contents and then the argument note; no filler sentences. The Args section slightly restates the first line's date scoping but stays brief.

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?

This is a simple one-parameter read with no output schema and no nested objects, and the description covers what it returns, which is most of what an agent needs. The remaining gap is edge-case behavior — an unset plan for a given date — which matters because a companion setter exists and implies the plan may be absent.

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?

Schema coverage is 0% — the schema only declares 'date' as an untyped-in-practice string — so the description carries the burden and does so by specifying the YYYY-MM-DD format and that it is a single day rather than a range. It adds meaningful format semantics beyond the schema.

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 ('Get nutrition plan/settings') scoped to a single date, and the second paragraph clarifies that the payload contains goals, calorie targets, macros, and plan configuration. It does not explicitly differentiate itself from set_nutrition_daily_settings, but the read-vs-write intent is unambiguous.

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

Usage Guidelines2/5

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

The description never says when to use this tool versus the obvious sibling set_nutrition_daily_settings, nor any prerequisite such as the plan needing to already exist. Usage is only implied by the word 'Get', which is minimal guidance.

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

Deploy Server

Other Tools