Skip to main content
Glama
Sign In
健康同步 MCP

健康同步 MCP

by asadman1523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

health_log_meal

Idempotent

Record a meal in a Fitbit/Google Health account with a dry-run preview by default and idempotency safeguards. Nutrition values can be left out.

Instructions

寫入飲食紀錄。營養數值可省略，缺少的數值不會補零；匿名食物新增後不可直接更新。

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_name": "<food_name>",
      "start_time": "<start_time>",
      "end_time": "<end_time>",
      "meal_type": "<meal_type>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "health_log_meal"
  }
}

Input Schema

NameRequiredDescriptionDefault
fat_gNo
carbs_gNo
dry_runNo預設只預覽。使用者要求實際寫入後設 false。
end_timeYes附時區的 RFC3339 時間，例如 2026-10-04T18:00:00+08:00；不可猜測缺少的時間。
servingsNo
food_nameYes
meal_typeYes
protein_gNo
start_timeYes附時區的 RFC3339 時間，例如 2026-10-04T18:00:00+08:00；不可猜測缺少的時間。
calories_kcalNo
idempotency_keyYes每筆來源紀錄的穩定唯一鍵；同一鍵不同資料會拒絕。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so safety is partly covered. The description adds genuine behavioral detail: missing nutrition values are not zero-filled, and anonymous foods cannot be updated after insertion (a notable immutability trait). It omits the dry_run preview-by-default behavior, which is central to calling this correctly.

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?

Three tight clauses with the purpose front-loaded and no filler. Efficient and on-point, though arguably over-terse given the tool's complexity.

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?

For an 11-parameter mutation tool with no output schema, the description is thin. It never mentions dry_run defaulting to preview-only (the single most important fact for an agent to invoke correctly), nor the timezone/idempotency semantics needed for safe writes. The description leaves significant gaps in the calling contract.

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 only 36%, so the description must compensate. It clarifies that nutritional values (fat_g, carbs_g, protein_g, calories_kcal, servings) are optional and not padded, but says nothing about dry_run, meal_type, the two timestamps, or idempotency_key beyond what the schema already documents. Partial compensation only.

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?

States a specific verb+resource: 寫入飲食紀錄 (write a meal record). This clearly distinguishes it from health_log_workout (logging exercise) at the resource level, though no sibling is named explicitly. Purpose is unambiguous.

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

Usage Guidelines2/5

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

No when-to-use vs when-not guidance and no routing to alternatives among the many health_* siblings (create/update/get/list). Notes that nutrition values may be omitted but provides no context about when this tool should be chosen over health_create or health_log_workout.

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

Deploy Server

Other Tools