MyFitnessPal MCP Server

by AdamWalt

Overview Schema Source Related Servers Discussions Admin

Python

Remote

mfp_delete_fast

DestructiveIdempotent

Delete a fasting entry by ID. Permanent removal—use only when certain, as recovery is impossible.

Instructions

Delete a fasting entry by id.

Destructive and not recoverable. The `id` must come from a prior
`mfp_log_fast` call or be captured from the MFP app — the MCP cannot
list existing fasts because MFP exposes no read endpoint.

Args:
    params: DeleteFastInput (id, response_format)

Returns:
    str: Confirmation with the deleted id and HTTP status

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already carry destructiveHint, and the description reinforces with 'Destructive and not recoverable', adding that deletion cannot be undone. It also discloses a platform constraint (no MFP read endpoint) and the return shape (deleted id and HTTP status), which goes beyond the structured fields.

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?

The description is compact and front-loaded: the action and destructiveness appear first, followed by the critical id-origin constraint, then Args/Returns. Every sentence earns its place with no redundant filler.

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

Completeness5/5

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

For a one-parameter destructive delete tool, this covers the essential operational context: irreversible effect, valid id provenance, inability to list existing fasts, and return value. With an output schema present, no further detail is needed for an agent to invoke it correctly.

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 description coverage is 0%, and the description compensates by saying the id identifies a fasting entry and must come from a prior mfp_log_fast call. However, response_format is only listed by name in Args with no added meaning, so the compensation is partial.

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?

Opens with a specific verb+resource: 'Delete a fasting entry by id' — clear and distinct from siblings like mfp_delete_meal. It also names the exact target (fasting entry) and the key dimension (id), so an agent immediately knows what this tool does.

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?

Provides explicit guidance on where the id must come from (prior mfp_log_fast or MFP app) and why listing is impossible, preventing a dead-end search. It does not name alternative tools for non-delete intents, but the prerequisite and limitation are clear enough for correct routing.

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