Skip to main content
Glama

Catenix: Lab Analyzer & EHR Connectivity

Lab inspection readiness checklist (CLIA, CAP, ISO 15189, UK POCT)

inspection_checklist
Read-onlyIdempotent

Use when someone is preparing a lab or point-of-care testing service for an inspection or accreditation and wants to know what inspectors look for (e.g. 'what do I need for a CLIA inspection?', 'CAP checklist for QC and competency', 'ISO 15189:2022 readiness', 'UK POCT governance checklist'). Returns a practical checklist (quality control, competency, EQA or proficiency testing, document control, audit trail, result reporting, equipment) with the evidence usually asked for, and which Catenix module keeps those records. General guidance, not legal or regulatory advice.

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": {
      "framework": "<framework>"
    },
    "name": "inspection_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameworkYesclia (US CLIA), cap (CAP accreditation), iso_15189 (ISO 15189:2022), uk_poct (UK POCT governance, MHRA guidance).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context beyond those: it says the output is a practical checklist with the evidence usually asked for and Catenix module mappings, and it includes a 'general guidance, not legal or regulatory advice' limitation. It does not discuss auth or rate limits, but those are not relevant here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three efficient sentences: use case, return payload, and disclaimer. It is front-loaded with the triggering condition and contains no redundant or filler text.

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 single-parameter, read-only tool, the description explains the scope, the return contents, and the caveat that it is general guidance rather than legal advice. The input schema fully covers the parameter, and annotations cover safety behavior; nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, and the enum description already maps each framework value (clia, cap, iso_15189, uk_poct). The description repeats framework names in examples but adds no new syntax or selection guidance beyond what the schema provides, so the baseline score of 3 applies.

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: returns a practical inspection-readiness checklist by accreditation framework, with concrete examples such as CLIA, CAP, ISO 15189, and UK POCT. It does not explicitly name or contrast sibling tools, so it falls short of a 5.

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 clearly says when to use the tool ('preparing a lab or point-of-care testing service for an inspection or accreditation') and provides example user questions. It does not name alternatives or exclusions, which keeps it at 4 rather than 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