Skip to main content
Glama
turnnoblindeye

Wellness Project MCP

update_lab_result

Idempotent

Correct mistakes in logged lab results by updating collection date, marker, value, unit, flag, notes, panel, or lab name. Select one row by ID or use date and marker to target the right result.

Instructions

Update one or more fields on an existing lab result. Use when the user wants to correct a result already logged, most often its collection date. Only send the fields that need to change; omit all others.

SELECTOR, pass exactly one of id, date, or date+marker:

  • id: addresses one marker's row. Any editable field may change.

  • date (optionally narrowed by panel_name): addresses every result from that draw at once. Only new_date, panel_name_new, and lab_name may change this way. result_value, result_unit, marker_name, flag, and notes are per-marker fields and require a single row, so one call can never overwrite every marker in a draw with the same value.

  • date + marker (a marker-name substring, case-insensitive, optionally narrowed by panel_name): resolves to one marker's row, same as id. Errors with candidate IDs if more than one marker on that date matches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoLab result ID. Selects a single marker row. Alternative to date.
dateNoCollection date of the draw to update. Format: YYYY-MM-DD. Selects every result from that draw, or (with marker) one row. Alternative to id.
flagNoNew lab flag: "H", "L", "HH", "LL", or "A". Optional, omit if not changing. Only allowed when selecting by id or date+marker.
notesNoNew notes. Optional, omit if not changing. Only allowed when selecting by id or date+marker.
markerNoOptional with date: marker-name substring, case-insensitive (e.g. "LDL"), narrowing the date selector to a single marker row so per-marker fields can be edited without an id. Ignored when id is given.
lab_nameNoNew lab name (e.g. "Quest Diagnostics", "LabCorp"). Optional, omit if not changing. Works with any selector.
new_dateNoNew collection date. Format: YYYY-MM-DD. Optional, omit if not changing. This is the main reason to call this tool, and it works with any selector.
panel_nameNoOptional, narrows a date (or date+marker) selector to one panel within that draw (e.g. "Lipid Panel"). Ignored when id is given.
marker_nameNoNew marker name. Optional, omit if not changing. Only allowed when selecting by id or date+marker.
result_unitNoNew unit of measurement (e.g. "mg/dL"). Optional, omit if not changing. Only allowed when selecting by id or date+marker.
result_valueNoNew numeric result value. Optional, omit if not changing. Only allowed when selecting by id or date+marker.
panel_name_newNoNew panel name. Optional, omit if not changing. Works with any selector.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesHuman-readable result text returned by the tool.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.2.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already provide idempotentHint and destructiveHint. The description goes beyond by explaining error behavior (e.g., 'Errors with candidate IDs if more than one marker matches') and the subtlety that per-marker fields cannot be changed via a date-only selector. It does not contradict any annotation.

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?

The description is longer than typical but every part is necessary to explain the complex selector logic and field restrictions. It is well-structured with a clear breakdown of selectors, making the length justified.

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?

Given the tool's complexity (12 parameters, 0 required, multiple selector modes), the description provides everything needed: selector rules, field constraints, error handling, and examples. The output schema is present, so return values don't need to be described. The description is fully self-contained for correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already has 100% description coverage. The description adds critical extra semantics on top, such as which fields are allowed only with id/date+marker, and how 'marker' and 'panel_name' narrow the selection. This goes well beyond the basic parameter descriptions.

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 ('Update') and resource ('lab result'), clearly distinguishing it from sibling tools like log_lab_results, list_lab_results, and delete_lab_result. The purpose is immediately clear.

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 says when to use it ('when the user wants to correct a result already logged'), and provides detailed selector logic (id vs date vs date+marker) with constraints on which fields are allowed per selector. This gives unambiguous guidance on how to invoke the tool correctly.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/turnnoblindeye/wellness-project-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server