Vaultbeat MCP Server

Overview Schema Source Related Servers Discussions Admin

Log symptom

log_symptom

Record one reported symptom per call with type, severity, timing, and suspected triggers to align it with sleep, food, heart rate, and temperature data.

Instructions

Record one symptom the person reports — one call per symptom (agent write).

This is where "我肚子疼" / "headache since lunch" / "拉肚子了" goes, not a note: each episode is kept as fields (type, severity, timing, place, suspected causes) so a later read can line it up with sleep, food, heart rate and wrist temperature. Two symptoms at once are two calls. This tool only ever adds; it cannot change or delete anything already recorded.

symptom_type: a short English token. Use the Apple Health name when one fits — abdominal_cramps, bloating, constipation, diarrhea, heartburn, nausea, vomiting, headache, dizziness, fatigue, fever, chills, coughing, sore_throat, runny_nose, lower_back_pain, chest_tightness_or_pain, shortness_of_breath, acne, night_sweats… — so it merges with what Apple Health imports; otherwise a plain descriptive one (rectal_bleeding, stomach_spasm, eye_strain). Any spelling is folded to one form. display_name: the person's own words, e.g. "便血" / "胃痉挛".

severity: mild | moderate | severe | unspecified. Use unspecified unless they said how bad it is — never grade it for them.

onset_at: when it began, ISO 8601 with their UTC offset, e.g. "2026-09-30T10:49+08:00". Omit it only for something happening NOW (it defaults to the current time). If they named a day but no time ("昨天头疼"), pass that day as a bare "2026-09-29" — do not invent an hour. end_at: when it eased, if they said; add it later with update_symptom. date: the local day to file it under, only when it differs from the onset's own day. body_location, note: free text, only what they said. triggers: what THEY suspect caused it, as short tokens (["bbq_dinner", "spicy_food"], ["sleep_deprivation"]). Record their suspicion; do not add causes of your own.

Returns entry_id (keep it for update_symptom / delete_symptom) and the entry as read back. Read everything with get_symptoms. Sealed for the owner and this machine only, end to end, before it leaves here.

Input Schema

TableJSON Schema

Name	Required	Default
`date`	No
`note`	No
`end_at`	No
`onset_at`	No
`severity`	No	unspecified
`triggers`	No
`display_name`	No
`symptom_type`	Yes
`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?

Annotations already declare destructiveHint=false and idempotentHint=false, but the description adds real context: it is strictly append-only ('cannot change or delete anything already recorded'), returns an entry_id to hand to update/delete, and is end-to-end sealed for the owner and machine. That is concrete behavior beyond the structured hints, with no contradiction.

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 purpose and the one-per-symptom rule, then organized field-by-field in visually scannable blocks using the exact parameter names. Given nine parameters and zero schema coverage the length is justified, though a few parenthetical asides (e.g. the trailing examples after the Apple Health list) could be trimmed.

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?

An output schema exists, so the description only needs to name the key return value, which it does ('entry_id ... and the entry as read back'). For a nine-parameter, 0%-schema-coverage mutation tool with no enums, the description closes every gap an agent would otherwise hit, including timezone handling and the do-not-invent severity/timing rules.

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 description coverage is 0%, so the description carries the full burden and does: it defines symptom_type naming conventions with merge rationale, supplies the severity enum (mild|moderate|severe|unspecified) that the schema lacks, and specifies ISO 8601 + UTC offset formats and edge-case defaults for onset_at, end_at, and date. It also constrains triggers to the user's own suspicion rather than invented causes.

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 ('Record one symptom the person reports') and immediately scopes the cardinality ('one call per symptom'). It explicitly distinguishes itself from log_note ('This is where ... goes, not a note') and names the sibling read/update/delete tools, so an agent can route without opening a schema.

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 explicit when-to-use rules ('Two symptoms at once are two calls'), explicit when-not ('not a note'), and names the alternatives with their conditions (update_symptom to add an end time later, get_symptoms to read, delete_symptom to remove). Routing is fully determined by the text.

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