Skip to main content
Glama

Catenix: Lab Analyzer & EHR Connectivity

Questions to ask when buying a LIS, middleware or lab interface

vendor_questions
Read-onlyIdempotent

Use when someone is choosing or buying a LIS, LIMS, POCT middleware or an analyzer-to-EHR interface and wants an RFP or a list of questions to ask vendors (e.g. 'what should I ask LIS vendors?', 'RFP questions for lab middleware', 'checklist for buying an HL7 interface'). Returns a copyable, vendor-neutral checklist grouped by connectivity, QC and compliance, security and privacy, data and audit trail, implementation and support, pricing, and contract and exit.

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": "vendor_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyingNoWhat they are buying. Default any.
groupsNoOnly these groups. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds that the output is a copyable, vendor-neutral checklist grouped into seven named categories, which is useful return-shape context with no output schema to carry it. It does not describe length, formatting, or citation depth, so it is good but not rich.

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?

A single front-loaded sentence: trigger condition first, example utterances in parentheses, then a concise statement of what is returned. Dense but every clause carries information; the only cost is that it reads as a long run-on rather than being split into trigger/return sentences.

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 simple read-only generator with two optional parameters, full schema coverage, and no output schema, the description supplies everything needed: when to invoke it, what the deliverable looks like, and how the deliverable is organized. 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by spelling out the seven group labels ('QC and compliance', 'security and privacy', 'data and audit trail', 'contract and exit') that map onto the terse enum values in the `groups` parameter. The `buying` parameter is only implicitly evoked by the mention of LIS, LIMS, middleware and interface, but the defaults are documented in the schema.

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 concrete verb-and-resource combination: it produces an RFP/vendor-question checklist for LIS, LIMS, POCT middleware or analyzer-to-EHR interface purchases. The resource (vendor questions for lab-system buying) is distinct from siblings such as inspection_checklist, compare_options or plan_lab_setup, so an agent can route to it without opening schemas.

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?

Gives a clear trigger condition ('Use when someone is choosing or buying a LIS...') plus three representative user phrasings that anchor intent matching. It does not state explicit exclusions or name a sibling to use instead, which keeps it short of a 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