Skip to main content
Glama

Catenix: Lab Analyzer & EHR Connectivity

Check if a lab analyzer connects to an EHR or LIS

check_connectivity
Read-onlyIdempotent

Use when someone asks whether a lab or point-of-care analyzer will connect to their EHR, LIS or practice system, or how to get analyzer results into the patient record without retyping (e.g. 'will my Sysmex XP-300 work with athenahealth?', 'connect Abbott i-STAT to Epic', 'Roche cobas b 101 to SystmOne', 'Siemens CLINITEK to EMIS', 'Tosoh AIA-900 to eClinicalWorks'). Fuzzy-matches the analyzer and the record system and returns: connection status (live, driver built, connectable via standard protocol with a published guide, or custom driver needed), the analyzer protocol (HL7 v2, ASTM, POCT1-A2), the physical link, how results pass through an on-site gateway, the record-system route, what is needed on site, questions to ask any vendor, and page links. Works for unknown analyzers too. 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": {
      "analyzer": "<analyzer>"
    },
    "name": "check_connectivity"
  }
}

Input Schema

NameRequiredDescriptionDefault
ehrNoEHR, LIS, LIMS or practice system, e.g. 'athena', 'eCW', 'Epic', 'SystmOne', 'EMIS Web'. Omit if not mentioned.
countryNoCountry of the site, e.g. 'UK' or 'US', if known.
analyzerYesAnalyzer make and/or model as the user wrote it, e.g. 'sysmex kx21n', 'i-STAT', 'Afinion 2'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations cover read-only, idempotent, non-destructive safety, and the description adds substantial behavioral detail: fuzzy matching, support for unknown analyzers, and the exact return categories (connection status, protocol, physical link, gateway, route, site needs, vendor questions, page links). This is well beyond what the annotations provide and does not contradict them.

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 front-loaded with the trigger and organized around the returned information, with no filler sentences. The long parenthetical list of five example queries and the dense return-field list make it slightly less tight than an ideal 5.

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 complex connectivity-lookup tool with no output schema, the description enumerates the relevant return fields, states what it does not do, and annotations cover safety. It is sufficiently complete for an agent to invoke it and interpret the result.

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 100%, so the baseline is 3. The description adds that analyzer and record system are fuzzy-matched and that unknown analyzers work, which clarifies matching behavior beyond the schema. It does not add meaning for the country parameter, so it is not a 5.

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 uses a specific trigger ('Use when someone asks whether a lab or point-of-care analyzer will connect to their EHR, LIS or practice system') and names the returned information, making the tool's core job clear. It does not explicitly contrast the tool with similarly named siblings such as get_ehr_integration, so sibling differentiation is inferred rather than stated.

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?

It gives a clear when-to-use trigger with concrete example queries and one boundary ('Does not interpret results'). It lacks explicit alternatives or guidance on when to prefer sibling tools such as get_ehr_integration or search_analyzers, so it is not a full 5.

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