Skip to main content
Glama

Catenix: Lab Analyzer & EHR Connectivity

Plan connecting several lab analyzers to an EHR or LIS

plan_lab_setup
Read-onlyIdempotent

Use when someone lists the analyzers in their lab or clinic and wants a plan for getting all their results into their EHR, LIS or practice system (e.g. 'we have a Sysmex XP-300, an i-STAT and an Afinion 2, how do we connect them to athenahealth?', 'plan the interfaces for our new urgent care lab', 'what do I need on site to connect these analyzers?'). Returns one plan: per analyzer the connection status (Driver built, Connection guide, or Catenix builds the driver, usually within a couple of days), the physical link (serial, network, USB or vendor software), protocol and what is needed on site; the on-site gateway and record-system route; patient matching; and a step-by-step go-live checklist. Renders an interactive Lab Map in ChatGPT and Claude. Does not interpret results.

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": {
      "analyzers": "<analyzers>"
    },
    "name": "plan_lab_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
ehrNoEHR, LIS or practice system, if known.
countryNoCountry, e.g. 'UK' or 'US'.
settingNoType of service, e.g. 'urgent care', 'private lab', 'GP practice'.
analyzersYesAnalyzer makes and models as the user wrote them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: the shape of the single returned plan, the fact that it renders an interactive Lab Map in ChatGPT and Claude, and the latency expectation that Catenix builds a missing driver 'usually within a couple of days.' It stops short of describing limits such as what happens with unrecognized analyzers beyond that fallback.

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 trigger condition is front-loaded in the first clause, followed by examples and then the return contents, so the reader can stop early. It is a single dense paragraph with a couple of parenthetical asides that could be trimmed, but nearly every clause 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?

There is no output schema, and the description compensates by enumerating the plan's sections and the interactive rendering. Combined with annotations covering safety and a fully documented input schema, an agent has everything needed to decide to call it and to describe the result.

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

Parameters3/5

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

Schema coverage is 100% and all four parameters carry descriptions, so the schema does the heavy lifting. The description confirms that analyzers are taken 'as the user wrote them' and that the EHR may be unknown, which adds mild meaning, but it gives no guidance on the country or setting fields or on how many analyzers can be batched.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it produces one connection plan per analyzer, covering connection status, physical link, protocol, gateway/record-system route, patient matching and a go-live checklist. That is far more precise than the title alone. It does not, however, distinguish itself from siblings such as recommend_lab_setup or compare_options, so an agent cannot tell from the text alone which of those to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is triggered explicitly with three realistic example utterances ('we have a Sysmex XP-300, an i-STAT and an Afinion 2, how do we connect them to athenahealth?'), plus a clear negative scope: 'Does not interpret results.' No alternative tool is named for the adjacent jobs, so the agent must infer that interpretation belongs elsewhere.

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