Skip to main content
Glama
Nutrition MCP
by ronkommoji

setup_profile

Create a nutrition tracking profile with weight, goal type, daily calorie and protein targets, and timezone to support accurate daily logging.

Instructions

Create the nutrition tracking profile used for daily goals and timezone-aware logging.

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": {
      "weight": "<weight>",
      "dailyCalorieGoal": "<dailyCalorieGoal>",
      "dailyProteinGoal": "<dailyProteinGoal>",
      "goalType": "<goalType>"
    },
    "name": "setup_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoUser name.
weightYesCurrent body weight.
goalTypeYes
timezoneNoIANA timezone, e.g. America/New_York.
weightUnitNolb
dailyCalorieGoalYesDaily calorie target.
dailyProteinGoalYesDaily protein target in grams.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it says nothing about behavior beyond the noun phrase 'Create' — not whether it fails or overwrites when a profile already exists, not required permissions, and not what the response contains. For an unannotated mutation tool this is a meaningful gap.

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?

A single front-loaded sentence with no filler or repetition of the tool name alone. It is efficient, though the terseness leaves no room for the behavioral detail this tool needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, 4 of them required, no annotations, and no output schema, the definition is too thin: it does not cover create semantics (conflict with an existing profile), the effect of weightUnit/goalType enums, or what is returned. The complexity of the tool outstrips what the description explains.

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 71%, so most fields are documented in the schema already. The description adds only a light gloss — 'daily goals' maps to the calorie/protein targets and 'timezone-aware logging' hints that timezone affects log timestamps — but gives no detail on enums like goalType, defaults like weightUnit, or units for weight.

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 states a specific verb and resource: 'Create the nutrition tracking profile,' and scopes it to daily goals and timezone-aware logging. It does not explicitly contrast with the sibling update_profile, so the create-vs-update distinction is left implicit.

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: the phrasing suggests first-time setup for goal tracking, but there is no statement of when to call this versus update_profile, nor any prerequisite about an existing profile. The agent must infer the initial-setup context.

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