Skip to main content
Glama
Fino-wind

Vaultbeat MCP Server

Add to strength log

log_strength_append

Append exercises and sets to an existing strength session without deleting or overwriting logged entries. Use it to add forgotten sets or log a workout in installments.

Instructions

Add exercises to a session WITHOUT touching what is already logged (agent write).

This tool cannot delete anything you did not send. Your exercises are appended to the day's existing session; an exercise whose name matches an existing one gets its sets appended to it. This is the right tool for "log the set I forgot" or for logging a session in installments while the owner is still in the gym — which is how strength data actually arrives.

Reach for log_strength_entry ONLY when you intend the supplied exercises to become the day's ENTIRE session and everything else to be deleted.

date is the LOCAL calendar day the session happened, "YYYY-MM-DD". exercises is [{"name": "卧推", "sets": [{"weightKg": 30, "reps": 8}, ...]}, ...].

This tool deliberately cannot set the session note: that field is replace-only, and a tool that promises to delete nothing must not carry an exception. Use log_strength_entry to change it.

The result is the same shape log_strength_entry returns. replaced_exercises is always [] here — that empty list is the receipt that this call deleted nothing. Encrypted end-to-end before it ever leaves this machine. Requires a bind made after the agent write path shipped; an older bind must re-pair by running uvx vaultbeat-apple-health@latest bind in a terminal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
exercisesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.8.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations confirm non-destructive, non-idempotent write, and the description adds substantial context beyond them: matching-name exercises get their sets appended, notes cannot be set (replace-only), auth/pairing requirement is documented, and encrypted end-to-end is disclosed.

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?

Front-loaded with the core behavior and the sibling contrast. Slightly verbose in the encryption/auth paragraph, but every sentence carries information (the pairing requirement is actionable).

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?

Output schema exists and the description confirms `replaced_exercises` is always `[]`, explaining its semantic meaning. Auth prerequisites, side effects on existing data, and the note-field restriction are all covered — nothing important is missing.

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?

Schema coverage is 0%, so the description carries full burden — and it delivers: `date` format ('YYYY-MM-DD' LOCAL calendar day) and full example of the `exercises` array structure with nested sets (weightKg/reps).

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?

States a specific verb and resource ('add exercises to a session') and clearly contrasts the behavior with the sibling `log_strength_entry` (append vs. full replace). An agent can immediately tell this apart from `log_strength_entry` and `log_food_append`.

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

Usage Guidelines5/5

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

Explicitly names when to use this tool ('log the set I forgot', logging in installments) and when NOT to use it ('Reach for `log_strength_entry` ONLY when...'), even describing the consequence of the wrong choice (everything else deleted).

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