Skip to main content
Glama

Catenix: Lab Analyzer & EHR Connectivity

Request a Catenix demo

request_demo

Sends the user's demo request to the Catenix team by email; the team replies to the address the user gives. This is the only tool that shares the user's personal details. Before calling it you MUST show the user every field you will send (name, email, organisation, country, analyzers, record system, message) and get their explicit confirmation in this conversation; then set user_confirmed to true. Never call it on your own initiative. The Catenix widget may call it only after it has shown the user every field and the user pressed Confirm and send. Do not guess missing fields: ask for them.

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": {
      "name": "<name>",
      "email": "<email>",
      "organisation": "<organisation>",
      "country": "<country>",
      "analysers": "<analysers>",
      "ehr": "<ehr>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "request_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
ehrYesEHR, LIS or practice system ('none' if none).
nameYesThe user's name.
emailYesThe user's work email.
countryYesCountry of the site.
messageNoAnything else the user wants to say.
analysersYesAnalyzers they run, comma separated.
organisationYesLab, clinic or company name.
user_confirmedYesTrue only after the user explicitly confirmed the exact details shown to them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the payload leaves the system by email, the reply goes to the user-supplied address, and this is the only tool that transmits personal data. That is a real disclosure the openWorldHint annotation alone would not convey. It stops short of saying what a successful or failed send returns, which keeps it off 5.

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-loaded with the side effect and the PII disclosure, then the mandatory confirmation protocol. The widget-specific sentence partly restates the agent confirmation rule, costing some tightness, but every sentence still carries actionable constraint.

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 7-required-parameter outbound side-effect with no output schema and no annotations for safety beyond readOnlyHint=false, the description supplies the critical missing pieces: the PII warning, the confirmation gate, and the no-guessing rule. The remaining gap is what the tool returns on success or validation failure, which the agent must discover empirically.

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 coverage is 100%, so all eight fields including ehr, analysers, and message are already documented, and the description correctly enumerates them as the set to show the user. It adds genuine meaning to user_confirmed ('true only after explicit confirmation') and to handling missing values rather than inventing them. A 4 rather than 5 because it adds no format or normalization guidance beyond the schema for the free-text fields.

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?

Specific verb and resource: 'Sends the user's demo request to the Catenix team by email,' plus the reply-routing detail. It also distinguishes itself from every read-only sibling by stating 'This is the only tool that shares the user's personal details.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly prescribes the preconditions (show every field, get explicit confirmation in-conversation, then set user_confirmed to true) and the prohibitions ('Never call it on your own initiative', 'Do not guess missing fields: ask for them'). It even covers the separate widget caller path, so an agent knows both when to use it and when not to.

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