Skip to main content
Glama

Check Ruminate health

health_check
Read-only

Verify local storage, schema, and model availability without changing data so you can confirm Ruminate is ready for imports, searches, and citations.

Instructions

Read local storage, schema and model availability without changing data.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so "without changing data" largely restates the read-only contract. The description does add scope beyond the annotations by naming the three subsystems probed (local storage, schema, model availability), which tells the agent this is a local diagnostic rather than a remote service ping. It says nothing about cost, failure semantics, or whether a degraded result still counts as a successful call.

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

Conciseness5/5

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

A single sentence with zero filler, front-loading the verb and the scope of the check. Nothing is repeated and nothing could be cut without losing information.

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?

The tool is simple (no params, rich annotations, and an output schema that carries the return values), so the description does not need to explain results. It lists what is inspected, which is the main thing an agent needs; the only minor omission is what invoking it implies operationally, such as whether it is cheap enough to call routinely.

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 there is no parameter meaning for the description to carry; baseline applies. The empty schema is consistent with the description's no-argument framing.

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 uses a specific verb ("Read") plus concrete resources (local storage, schema, model availability), so an agent can tell this is a diagnostic/readiness probe rather than a data-retrieval call like get_claim or search_sources. It stops short of naming the health/readiness concept explicitly (that lives only in the title), so the sibling differentiation is implicit rather than stated.

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

Usage Guidelines2/5

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

"without changing data" is a safety statement, not usage guidance. Nothing says when to call this (e.g. before a long-running operation, on connection errors) or when not to bother, and no alternative sibling is named despite there being eight other tools it could be confused with.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.