Vaultbeat MCP Server

Overview Schema Source Related Servers Discussions Admin

Update symptom (overwrites given fields)

update_symptom

Destructive

Modify a logged symptom entry by ID to record changes such as resolution, worsening severity, notes, or triggers; only supplied fields change.

Instructions

Change fields of one reported symptom (agent write) — e.g. it eased.

The common call is update_symptom(entry_id, end_at="…") when the person says it has stopped, or a new severity when it got worse. Only the fields you pass change; omitted ones keep their value. Passing a field OVERWRITES it: note replaces the old note rather than adding to it, and triggers replaces the whole list — read the entry first and send the combined list if you mean to add one. "" clears a text field or a mistaken end_at; [] clears triggers.

entry_id comes from log_symptom or from get_symptoms' reported list. Symptoms imported from Apple Health cannot be edited here.

Returns previous — the old value of every field this call changed — and the entry as read back.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No
`note`	No
`end_at`	No
`entry_id`	Yes
`onset_at`	No
`severity`	No
`triggers`	No
`display_name`	No
`symptom_type`	No
`body_location`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.9.1Oct 3, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Despite annotations covering the safety profile (destructiveHint=true, idempotentHint=false), the description adds critical behavior beyond annotations: overwrite semantics (note replaces rather than appends, triggers replaces the whole list), clearing conventions ('' and []), the read-back contract (returns previous plus entry as read back), and an edit restriction for Apple Health imports. This is exactly the extra context needed for a destructive, non-idempotent mutation.

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 common call and its trigger, then layers overwrite, clearing, sourcing, and return semantics. Every paragraph earns its place, though it runs several dense sentences and could tighten slightly.

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 10-param, 0%-coverage destructive mutation with an output schema, the description covers the partial-update model, overwrite/clear rules, id sourcing, edit exclusions, and return shape. Nothing an agent needs to call it correctly 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 must carry parameter meaning. It supplies the critical partial-update semantics ('only the fields you pass change; omitted ones keep their value'), explains entry_id sourcing, and defines special values ('' clears text/end_at, [] clears triggers). This is substantially more than the bare schema titles.

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 (change fields) and resource (one reported symptom), clarifies it targets a single entry by entry_id, and differentiates from siblings like log_symptom and delete_symptom by noting it only modifies given fields.

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?

Gives concrete when-to-use examples ('when the person says it has stopped' → end_at, 'when it got worse' → severity) and explicitly excludes a case: symptoms imported from Apple Health cannot be edited here. Names the source tools for entry_id (log_symptom, get_symptoms).

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