Skip to main content
Glama
MyFitnessPal MCP Server

MyFitnessPal MCP Server

by delize

mfp_get_water

Read-onlyIdempotent

Retrieves water intake for a specific date, defaulting to today, so you can track daily hydration in milliliters.

Instructions

Get water intake for a specific date.

MyFitnessPal's /food/water endpoint returns the amount in a field named milliliters (python-myfitnesspal's _get_water), so day.water is always ml regardless of the account's display unit.

Args: params: GetWaterInput containing: - date (str, optional): Date in YYYY-MM-DD format, defaults to today

Returns: str: Water intake amount for the specified date

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": {
      "params": "<params>"
    },
    "name": "mfp_get_water"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and non-destructive, so the bar is lower, but the description adds real value by disclosing that the value is always in milliliters regardless of the account's display unit and explaining why (the underlying `/food/water` field is `milliliters`). That is exactly the kind of context an agent would otherwise get wrong; it does not cover error behavior or what happens with future dates.

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?

The operative statement is front-loaded in the first sentence, and the endpoint rationale earns its place by justifying the milliliter guarantee. The reference to python-myfitnesspal's `_get_water` is slightly indulgent but short enough not to distract.

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?

An output schema exists, so return formatting need not be spelled out, and the one genuinely ambiguous aspect — the unit — is explicitly resolved. A brief note on whether future dates or missing entries return zero versus an error would make it fully complete for a single-param read tool.

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?

With one parameter, the description restates the YYYY-MM-DD format and the default-to-today behavior, which largely duplicates the schema's own `date` description. It does not explain the required `params` wrapper object, so it adds only marginal meaning beyond the structured field.

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 first sentence gives a specific verb and resource ('Get water intake') plus the scope ('for a specific date'), which cleanly separates it from mfp_set_water and the broader mfp_get_diary. It never names a sibling tool explicitly, so it stops short of full differentiation.

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 reader infers this is the read-side counterpart to mfp_set_water. There is no explicit 'use this when...' statement, no mention of when to prefer mfp_get_diary instead, and no prerequisites or auth notes.

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