Skip to main content
Glama
Datris MCP Server

Datris MCP Server

check_service_health

Check whether PostgreSQL, MongoDB, MinIO, ActiveMQ, Kafka, and configured vector databases are up, down, or not configured before search or query operations.

Instructions

Check which backend services are up, down, or not configured. Returns the health status of PostgreSQL, MongoDB, MinIO, ActiveMQ, Kafka, and any configured vector databases (Qdrant, Weaviate, Milvus, Chroma, pgvector). Call this before attempting search or query operations to know which services are available.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden; it does convey that results include a third 'not configured' state, which prevents misreading absent services as outages. It does not say whether the check is a live probe versus cached, whether it can be slow or time out when a service is unreachable, or whether it requires credentials — meaningful gaps for a diagnostic tool, though the read-only nature is self-evident from 'check'.

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?

Three sentences, front-loaded with the purpose and ending with the actionable instruction, so the most decision-relevant content lands first. The parenthetical list of six vector databases is somewhat long but earns its place by telling the agent exactly which backends can appear in the result.

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?

There is no output schema, so the description must characterize the return values, and it does by naming the per-service status vocabulary (up/down/not configured). What remains unstated is the response shape (per-service object versus flat list) and any aggregation or summary field; for a zero-parameter health check this is a small residual gap rather than a blocker.

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?

The input schema has zero parameters, so there are no parameter semantics to explain and the baseline of 4 applies. The description correctly adds no parameter noise.

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?

The description names a specific verb ('check') and resource ('backend services'), then enumerates the exact systems covered (PostgreSQL, MongoDB, MinIO, ActiveMQ, Kafka, and the vector DBs). It also states the possible outcome states ('up, down, or not configured'), so an agent knows precisely what this tool reports and can distinguish it from the data/search siblings.

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 gives an explicit trigger: 'Call this before attempting search or query operations to know which services are available', which is actionable pre-flight guidance. It stops short of stating when-not to call it (e.g. if a prior check already succeeded, or if the operation is non-query) and names no alternative tool, so it falls 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.

Deploy Server

Other Tools