Skip to main content
Glama
collapseindex

CI-1T Prediction Stability Engine

health

Verify the engine is reachable and responsive by checking status, version, and latency before performing evaluations or fleet operations.

Instructions

Check CI-1T engine health. Response: { status, version, latency_ms }. Call before evaluate/fleet operations to verify the engine is reachable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The health tool handler implementation. Calls the CI-1T backend fleet-session endpoint with { action: 'health' }, requires API key authentication, and returns engine status (status, version, latency_ms).
    server.tool(
      "health",
      "Check CI-1T engine health. Response: { status, version, latency_ms }. Call before evaluate/fleet operations to verify the engine is reachable.",
      {},
      async () => {
        const guard = requireApiKey();
        if (guard) return guard;
        const result = await apiFetch("/api/fleet-session", {
          method: "POST",
          headers: apiKeyHeaders(),
          body: { action: "health" },
        });
        return formatResult(result);
      }
    );
  • Empty schema object — the health tool takes no input parameters (no Zod schema defined).
    {},
  • src/index.ts:593-607 (registration)
    Registration of the 'health' tool via server.tool() with the description 'Check CI-1T engine health.'
    server.tool(
      "health",
      "Check CI-1T engine health. Response: { status, version, latency_ms }. Call before evaluate/fleet operations to verify the engine is reachable.",
      {},
      async () => {
        const guard = requireApiKey();
        if (guard) return guard;
        const result = await apiFetch("/api/fleet-session", {
          method: "POST",
          headers: apiKeyHeaders(),
          body: { action: "health" },
        });
        return formatResult(result);
      }
    );
Behavior4/5

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

Describes the response format (status, version, latency_ms) implying read-only, no side effects. Could explicitly state non-destructive nature, but sufficient for a health check.

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?

Two efficient sentences, front-loaded with purpose and response format. No wasted words.

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 no-parameter, no-output-schema tool, the description provides all necessary context: purpose, response format, and usage timing.

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?

No parameters exist, so description need not add parameter info. Baseline 4 applies as schema coverage is 100% and no parameters require explanation.

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?

Clearly states the tool checks CI-1T engine health with specific response fields. Distinguishes from sibling tools like evaluate and fleet_evaluate by being a pre-operation health check.

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 advises calling before evaluate/fleet operations to verify engine reachability, providing clear usage context and when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/collapseindex/ci-1t-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server