Garmin MCP Server

Overview Schema Source Related Servers Discussions Admin

delete_custom_food

Remove a custom food from your Garmin nutrition library permanently. Obtain the food ID via get_custom_foods, and ensure it is not used in any logged meal.

Instructions

Delete a custom food from the user's Garmin nutrition library

Permanently removes a custom food entry. The food must not be actively referenced in a logged meal to be deleted. Use get_custom_foods to find the foodId.

Args: food_id: ID of the custom food to delete — a 32-char hex string (from get_custom_foods or create_custom_food)

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": {
      "food_id": "<food_id>"
    },
    "name": "delete_custom_food"
  }
}

Input Schema

Name	Required	Description	Default
`food_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations present, the description carries the burden. It discloses the permanent nature of the deletion and the requirement that the food not be in active use, which are important behavioral traits. It does not cover error handling or side effects, but the essential behaviors are clearly stated.

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 concise, starting with the purpose, then a brief note on constraints, and finally a clear Args section. No redundant information or filler; every sentence contributes to understanding the tool's use.

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?

Given the output schema exists, the description need not explain return values. It includes the essential context: action, resource, ID sourcing, and a critical precondition. It lacks explicit error scenarios but remains sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter food_id is fully described: it identifies the custom food to delete, is a 32-char hex string, and can be obtained from get_custom_foods or create_custom_food. This adds substantial meaning beyond the schema's bare type definition.

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?

Clearly states it deletes a custom food from the user's Garmin nutrition library, using the verb 'delete' and specifying the resource (custom food). It also adds the key detail that deletion is permanent, fully covering the action's intent.

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 to use get_custom_foods to find the foodId, and mentions the precondition that the food must not be actively referenced in a logged meal. This gives clear context on when and how to use the tool, though it doesn't mention alternative tools for non-deletion operations.

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

Deploy Server