Skip to main content
Glama

Catenix: Lab Analyzer & EHR Connectivity

Recommend lab or clinic testing software setup

recommend_lab_setup
Read-onlyIdempotent

Use when someone asks what LIS, LIMS or point-of-care testing software a small lab, clinic, urgent care, occupational health provider, pharmacy, GP practice, physician office or wellness clinic should use, or how to set up analyzer connectivity, QC and reporting for their setting (e.g. 'what LIS should my small lab use?', 'do I need a LIS to get analyzer results into my EHR?', 'software for a clinic that tests blood on site'). Returns the usual architecture for that setting, the modules that fit (connectivity, QC with Westgard rules and lockout, operator competency, EQA, audit trail, reports, billing, multi-site), status of each listed analyzer, the record-system route, how setup works, what is needed on site, the pricing model (no prices are quoted), and questions to ask any vendor.

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": {
      "setting": "<setting>"
    },
    "name": "recommend_lab_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
ehrNoTheir EHR, LIS or practice system, if known.
countryNoCountry, e.g. 'UK' or 'US'.
settingYesType of service, e.g. 'private lab', 'urgent care', 'occupational health', 'pharmacy', 'GP practice'.
analyzersNoAnalyzers they run or plan to run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it enumerates the return payload (architecture, modules, analyzer status, record-system route, on-site requirements, pricing model) and explicitly states no prices are quoted, which prevents a downstream agent from expecting quotes.

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 phrase is front-loaded and every clause carries information about trigger conditions or return contents. However, it is one very long multi-clause sentence with a dense parenthetical list of examples and a second paragraph-length list of return items, which would scan better as short structured bullets.

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, so the description must carry the return contract — and it does, listing architecture, fitted modules, analyzer status, record-system route, setup steps, on-site needs, pricing model and vendor questions. Combined with the explicit setting examples and the no-prices disclaimer, an agent has everything needed to call and interpret 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%, so setting, analyzers, ehr and country are all documented in the schema, which sets the baseline at 3. The description does add some value by enumerating concrete setting values (small lab, urgent care, occupational health, pharmacy, GP practice, physician office, wellness clinic) in the absence of any enum, but it says nothing about how analyzers or ehr inputs change the answer.

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?

Names a specific verb and resource (recommend LIS/LIMS/point-of-care software setup) and enumerates the settings it covers plus three sample user questions, so an agent can pattern-match a request to this tool immediately. It is clearly a recommendation/architecture tool, distinct from the narrower sibling capabilities like check_connectivity or compare_options.

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?

"Use when someone asks what LIS, LIMS or point-of-care testing software ... should use, or how to set up analyzer connectivity, QC and reporting" is an explicit, quotable trigger with concrete example phrasings. It stops short of naming when NOT to use it or pointing at siblings such as compare_options or get_platform_capability for narrower follow-ups.

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