FatSecret MCP Server

add_saved_meal_item

Add a food item to a previously saved meal by specifying the food ID, serving size, and quantity. Helps you update meal plans by including new ingredients without creating a new meal.

Instructions

Add a food item to a saved meal. Requires profile auth (check_auth_status first).

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": {
      "saved_meal_id": "<saved_meal_id>",
      "food_id": "<food_id>",
      "saved_meal_item_name": "<saved_meal_item_name>",
      "serving_id": "<serving_id>",
      "number_of_units": "<number_of_units>"
    },
    "name": "add_saved_meal_item"
  }
}

Input Schema

Name	Required	Description
`food_id`	Yes	Food ID to add
`serving_id`	Yes	Serving ID
`saved_meal_id`	Yes	Saved meal ID
`number_of_units`	Yes	Number of serving units
`saved_meal_item_name`	Yes	Item name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.9Aug 18, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations indicate this is a mutation (readOnlyHint=false, idempotentHint=false). The description adds value by noting the authentication requirement, but does not disclose other behavioral traits such as side effects (e.g., duplicate handling), error conditions, or success/failure responses, which are important for an agent to invoke correctly.

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 extremely concise with two short sentences: one stating the action and one stating a prerequisite. There is no wasted text, and the most important information is front-loaded.

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?

Given the complexity (5 required parameters, no output schema), the description is incomplete. It does not explain what the tool returns, how the parameters interact, validation rules, or potential failure modes. An agent needs more context to confidently use this mutation 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?

Schema description coverage is 100%, with brief descriptions for all five parameters. The tool description does not add additional meaning beyond the schema, such as parameter relationships, constraints, or valid ranges, so it meets the baseline for high schema coverage without extra clarification.

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 clearly states the action 'Add a food item to a saved meal' with a specific verb and resource. However, it does not explicitly differentiate from sibling tools like edit_saved_meal_item or delete_saved_meal_item, leaving some ambiguity for the agent about when to choose this specific tool.

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?

The description mentions a prerequisite ('Requires profile auth (check_auth_status first)') which provides some context, but it lacks guidance on when to use this tool versus alternatives (e.g., copy_saved_meal_entries, create_food_entry) and does not indicate when not to use it.

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

Deploy Server