Skip to main content
Glama

foodose GLP-1 nutrition

GLP-1 daily targets

calculate_glp1_target
Read-onlyIdempotent

Daily calorie, protein, carbohydrate, fat and fibre targets for someone taking a GLP-1 receptor agonist, plus the appetite ceiling: a dose aware estimate of the most they are likely to manage in a day. Use it for anyone taking or considering one of these medications, where a standard calorie calculation would assume an appetite they do not have. Returns the full derivation with a PubMed citation per step. The engine is the one behind the Foodose iPhone app, which applies it every morning to plate a day of food around the user's dose week. Educational only. Not medical advice, not a diagnosis, and not a substitute for the clinician who prescribes the medication. Not appropriate for pregnancy, breastfeeding, insulin or sulfonylurea use, a history of disordered eating, or anyone under 18.

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": {
      "weightKg": "<weightKg>",
      "heightCm": "<heightCm>",
      "age": "<age>"
    },
    "name": "calculate_glp1_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYes
sexNoBiological sex, which sets the BMR constant.female
goalNolose
doseMgNoCurrent dose in mg. Must be a licensed dose for that medication, otherwise it is treated as 0. Use get_appetite_ceiling to list the licensed doses.
activityNolight
heightCmYesHeight in centimetres.
weightKgYesCurrent weight in kilograms.
medicationNoBrand name, any case. Generic names map to the weight-management brand: semaglutide to Wegovy, tirzepatide to Zepbound, liraglutide to Saxenda, dulaglutide to Trulicity, oral semaglutide to Rybelsus.undecided
goalWeightKgNoDefaults to 85 percent of current weight.
weeklyLossKgNo
startWeightKgNoWeight when the medication was started, used for the adaptive thermogenesis step.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / medication / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "ozempic",
      +      "wegovy",
      +      "mounjaro",
      +      "zepbound",
      +      "saxenda",
      +      "trulicity",
      +      "rybelsus",
      +      "undecided"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • addedInput schema / properties / medication / description
      Added value: +"Brand name, any case. Generic names map to the weight-management brand: semaglutide to Wegovy, tirzepatide to Zepbound, liraglutide to Saxenda, dulaglutide to Trulicity, oral semaglutide to Rybelsus."
    • removedInput schema / properties / medication / enum
      Removed value: -[
      -  "ozempic",
      -  "wegovy",
      -  "mounjaro",
      -  "zepbound",
      -  "saxenda",
      -  "trulicity",
      -  "rybelsus",
      -  "undecided"
      -]
    • removedInput schema / properties / medication / type
      Removed value: -"string"
    • addedInput schema / properties / sex / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "female",
      +      "male"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / sex / enum
      Removed value: -[
      -  "female",
      -  "male"
      -]
    • removedInput schema / properties / sex / type
      Removed value: -"string"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them: it discloses the return shape (full derivation with a PubMed citation per step), the provenance of the engine, and the safety/liability boundaries. That is exactly the context an agent needs to decide whether to surface this result to a user.

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, then usage, then return value, then disclaimers — a sensible order. The safety footer is slightly padded ('Educational only' followed by three restatements of the same idea), but for a health tool that redundancy is defensible rather than wasteful.

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?

With 11 parameters, no output schema and partial schema coverage, the description does the important work: it explains what is returned, why the calculation differs from a standard one, and who should not use it. It stops short of describing the optional inputs and their defaults, which the schema handles but only partially.

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 64% and the description adds no parameter-level meaning beyond the concept of dose awareness. Optional inputs like goal, weeklyLossKg, startWeightKg and goalWeightKg are left entirely to the schema, so the baseline 3 for a reasonably documented schema is appropriate.

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?

Names a specific computation and its complete output set: calorie, protein, carbohydrate, fat and fibre targets plus an appetite ceiling. It also scopes it to a population (GLP-1 users) and implicitly separates it from get_appetite_ceiling, which returns only the ceiling.

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

Usage Guidelines4/5

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

Explicit use condition ('anyone taking or considering one of these medications, where a standard calorie calculation would assume an appetite they do not have') and an unusually clear exclusion list: pregnancy, breastfeeding, insulin/sulfonylurea, disordered eating history, under 18. It does not explicitly name get_appetite_ceiling as the narrower alternative, leaving that routing to the schema.

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