Skip to main content
Glama

health_check

Read-onlyIdempotent

Verify that the Lawstronaut MCP server and its backing services (database, cache) are reachable and responding. Returns the overall status, per-service status, server version, and a UTC timestamp.

When to use: Call at the start of a session to confirm connectivity before running any data tools, or when a previous tool call returned an unexpected error and you want to diagnose whether the service itself is down. When not: Do not call on every tool invocation — use it only for diagnostic purposes. It does not return legal data.

Parameters: Takes none — invoke with {}. No filters, pagination, or auth-scoped data.

Behavior: Read-only: one lightweight SELECT 1 against the database and one PING against the cache. Does not create, update, or delete any records. Auth: tools/call requires OAuth 2.0 or a Bearer token (401 if missing, invalid, revoked, or no active subscription). Rate limits: none at the MCP layer; safe to retry. If the database is unreachable the overall status will be 'degraded'. If only the cache is unreachable the overall status will be 'degraded'. Both must be healthy for status 'ok'.

Returns: status ('ok' | 'degraded'), version string, utc_timestamp, and a services object with db and cache each reporting their own status ('ok' | 'error') plus optional latency_ms.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
statusYesOverall health status
versionYesMCP server version
servicesYes
utc_timestampYesUTC timestamp of the health check

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description goes well beyond them: it discloses the exact operations (SELECT 1 and PING), the auth requirement (OAuth 2.0 or Bearer token, 401 on missing/invalid/revoked/no subscription), the absence of rate limits, retry safety, and the degradation semantics for each failure mode.

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 purpose and organized into labeled sections (When to use, Parameters, Behavior, Returns), which is easy to scan. Minor waste: the two sentences about database-only and cache-only failure both concluding 'degraded' are redundant, and the Returns section restates an existing output schema.

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 zero-parameter diagnostic tool this is complete: it covers invocation, auth, retry behavior, failure semantics, and status values. The presence of an output schema means the description did not need return details, so including them is surplus rather than a gap.

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 tool takes zero parameters, so the baseline is 4; the description reinforces this with 'Takes none — invoke with {}. No filters, pagination, or auth-scoped data.' That is adequate but simply restates what the empty schema already says.

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 specific verb and resource: verifying that the Lawstronaut MCP server and its backing services (database, cache) are reachable and responding. It also explicitly distinguishes itself from the sibling data tools by noting 'It does not return legal data', which no other sibling does.

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?

Provides an explicit 'When to use' (session start, or after an unexpected error from another tool) and 'When not' (not on every tool invocation). This gives the agent a clear routing rule against all 18 data-oriented siblings.

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.