Skip to main content
Glama

Catenix: Lab Analyzer & EHR Connectivity

Search connectable lab and point-of-care analyzers

search_analyzers
Read-onlyIdempotent

Use when someone wants to know which lab or point-of-care analyzers can be interfaced, or browses by maker or test type (e.g. 'which HbA1c analyzers can connect to an EHR?', 'Abbott analyzers with an HL7 interface', 'blood gas analyzers with LIS connectivity', 'Sysmex hematology', 'Roche cobas', 'Siemens', 'Tosoh'). Returns matching analyzers with connection status, protocol and guide links. Categories: chemistry, immunoassay, blood gas, molecular, haematology, urinalysis, coagulation, HbA1c.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_analyzers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 25.
queryNoFree text: model, maker, test type or protocol.
statusNoOnly return analyzers with this status.
categoryNoTest category, e.g. 'haematology', 'blood gas', 'urinalysis', 'hba1c'.
manufacturerNoManufacturer filter, e.g. 'Abbott', 'Sysmex', 'Roche'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/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 value by disclosing the return payload ('connection status, protocol and guide links'), which annotations cannot convey and no output schema exists to document. It stops there — no note on result caps beyond the schema's limit, ranking, or what happens with zero matches.

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-loads the trigger condition with 'Use when...' and then supplies examples that clarify scope, which earns the length. The trailing run of bare manufacturer names is repetitive filler and the first sentence is an overstuffed clause chain, but nothing essential is buried.

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?

For an optional-parameter, read-only search with full schema documentation and no output schema, the description does the important extra work: it names the return fields and the category space. Only pagination/limit behaviour and empty-result behaviour are left unstated.

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 every parameter's meaning is already documented, setting the baseline at 3. The description reinforces the free-text query dimension with worked examples and enumerates the legal category values, but adds no syntax, matching behaviour, or interaction rules between query and the filter parameters.

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 ('search lab or point-of-care analyzers') plus the precise qualifier 'can be interfaced', which distinguishes it from sibling tools like check_connectivity or get_ehr_integration. The concrete query examples and category taxonomy make the scope unambiguous.

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?

Explicitly says when to use it ('when someone wants to know which analyzers can be interfaced, or browses by maker or test type') and illustrates with realistic phrasings. It does not, however, name alternatives or state when a different sibling (e.g. compare_options, check_connectivity) would be the better call.

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