Skip to main content
Glama

Catenix: Lab Analyzer & EHR Connectivity

Lab QC, compliance and clinic software features

get_platform_capability
Read-onlyIdempotent

Use when someone asks about software for lab quality control and compliance or running a testing clinic: QC with Westgard rules and Levey-Jennings charts, QC lockout, operator competency, EQA or proficiency testing, audit trail, CLIA, CAP or ISO 15189 readiness, reagent lot tracking, equipment maintenance and temperature logs, multi-site oversight, patient registration, reports, billing, or HL7/ASTM/POCT1-A2 interfaces. Returns the matching modules, whether each is included or an add-on, and links.

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": {
      "topic": "<topic>"
    },
    "name": "get_platform_capability"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesFeature or problem, e.g. 'Westgard QC lockout', 'operator competency', 'EQA', 'audit trail'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds value beyond that by disclosing the shape of the result (matching modules, included vs. add-on, links), which is what an agent needs to decide how to present the answer.

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

Conciseness3/5

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

The trigger clause is correctly front-loaded, but the body is a single comma-spliced list of roughly thirty feature terms with no grouping. The vocabulary aids matching, yet the run-on structure makes it harder to scan than a short grouped list would be.

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 a single-parameter, read-only, closed-world lookup with no output schema, the description supplies both the domain scope and the return contents. Nothing essential to correct invocation is missing, though the lack of an output schema means the return description carries the whole burden and could be slightly more precise.

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?

Only one parameter exists and the schema documents it at 100% coverage with its own examples. The long feature list indirectly signals acceptable topic phrasing, but it reads as scope rather than parameter guidance, so the baseline of 3 holds.

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 names a concrete subject (software features for lab QC/compliance/clinic operations) and states the return payload: matching modules, inclusion vs. add-on status, and links. It does not name a sibling to contrast with (e.g. compare_options or recommend_lab_setup), so the boundary is inferable but not explicit.

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?

The opening clause gives a clear triggering condition ('Use when someone asks about software for lab quality control and compliance or running a testing clinic'), which is strong usage context. It stops short of stating when not to use it or which sibling to pick for comparison or setup recommendations.

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