Skip to main content
Glama
health-os

health-os

stage_lab_panel

Stage an extracted lab panel (PENDING). panel_date: YYYY-MM-DD from the report. rows: a list of {raw_name, value, unit, ref_min, ref_max}; value is a number — a printed "6,4" is read as 6.4, and a qualitative result ("negative", "not…

Instructions

Stage an extracted lab panel (PENDING). panel_date: YYYY-MM-DD from the report. rows: a list of {raw_name, value, unit, ref_min, ref_max}; value is a number — a printed "6,4" is read as 6.4, and a qualitative result ("negative", "not detected") or a limit ("<0.5") goes in as text (or pass it as value_text). Critical values are alerted immediately. Names not in the catalog (or whose unit can't belong to the matched marker) are stored UNMAPPED and pending — resolve them with map_pending_observation. Afterwards — show the table to the user and wait for an explicit approve_staged_source.

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": {
      "panel_date": "<panel_date>",
      "rows": "<rows>"
    },
    "name": "stage_lab_panel"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
facilityNo
panel_dateYes
panel_typeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, non-destructive, open-world, non-idempotent), and the description adds meaningful traits: items are stored PENDING, critical values trigger immediate alerts, and unrecognized markers land in an UNMAPPED queue rather than failing. It doesn't discuss duplicate staging or idempotency behavior, which is the remaining gap.

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 action and the required date/rows contract, then the parsing rules, then the workflow. Dense and largely waste-free, though the row-parsing sentence is a run-on that could be split for scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the staging/approval lifecycle is fully described. The only omissions are the two optional metadata parameters (facility, panel_type), whose semantics an agent must guess.

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?

Schema description coverage is 0%, so the description carries the load, and it does well for the hard parts: panel_date format, the row object shape (raw_name, value, unit, ref_min, ref_max), numeric parsing of comma decimals, and the qualitative/limit escape hatch via value_text. However, facility and panel_type are never explained.

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 ('Stage an extracted lab panel') plus the resulting state (PENDING), and immediately distinguishes itself from map_pending_observation and approve_staged_source by naming them in context.

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 routes the agent: unmapped/unit-mismatched names should be resolved with map_pending_observation, and the tool must be followed by showing the table and waiting for an explicit approve_staged_source. The sequencing is unambiguous.

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