Skip to main content
Glama

Catenix: Lab Analyzer & EHR Connectivity

Estimate time spent retyping lab results

estimate_time_saved
Read-onlyIdempotent

Use when someone wants to know how much staff time manual entry of analyzer results costs them, or would be saved by connecting analyzers to the EHR or LIS (e.g. 'we run 80 tests a day and typing each result takes 2 minutes, how much time is that?', 'is it worth interfacing our analyzers?'). Uses only the user's own numbers (tests per day, minutes of manual entry per result, sites, optionally results per test, working days and their own error rate) and returns hours per day, month and year and entries not retyped. Adds no benchmarks, prices or error statistics; without an error rate from the user it makes no error estimate.

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": {
      "tests_per_day": "<tests_per_day>",
      "minutes_per_result": "<minutes_per_result>"
    },
    "name": "estimate_time_saved"
  }
}

Input Schema

NameRequiredDescriptionDefault
sitesNoNumber of sites, default 1.
tests_per_dayYesTests per day (per site unless tests_per_day_is_total).
results_per_testNoResults produced per test (panels give several). Default 1.
error_rate_percentNoThe user's own transcription error rate in percent. Omit unless the user gives it.
minutes_per_resultYesMinutes of manual entry per result.
tests_per_day_is_totalNoTrue if tests_per_day is the total across all sites.
working_days_per_monthNoWorking days a month. Default 21.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/closed-world, so the safety profile is covered; the description then adds the behavior that matters — it computes solely from user inputs, refuses to inject benchmarks, prices or external error statistics, and degrades gracefully by omitting the error estimate when no rate is given. It even names the return shape (hours per day, month, year and entries not retyped).

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 'use when' trigger, followed by input scope, outputs and exclusions — no filler sentences. It is dense, with long embedded clauses and parenthetical examples, but every element carries information an agent needs.

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 pure read-only calculator with no output schema, the description covers trigger, required vs optional inputs, defaults semantics, the refusal conditions, and even the return values. Nothing an agent needs in order to call it correctly or to handle a user without an error rate is missing.

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 coverage is 100%, so baseline is 3, but the description adds meaning by enumerating the input set the calculation relies on (tests per day, minutes per result, sites, optional results per test, working days, user's own error rate) and by flagging error_rate_percent as user-only rather than something to assume. It does not explain tests_per_day_is_total or the default assumptions, which the schema handles instead.

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+resource: estimate staff time/manual-entry cost and the time saved by interfacing analyzers to the EHR/LIS. It also scopes itself against the recommendation/comparison siblings by declaring it 'adds no benchmarks, prices or error statistics' — a pure calculator using the user's numbers, which an agent can distinguish from tools like compare_options or recommend_lab_setup.

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 utterance-level triggers ('we run 80 tests a day and typing each result takes 2 minutes...', 'is it worth interfacing our analyzers?') that map directly to how users phrase requests. It also states an explicit negative condition: without a user-supplied error rate it makes no error estimate, and error_rate_percent should only be supplied when the user provides it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources