Skip to main content
Glama

aiana_health

Check connection status and latency for the semantic memory layer, ensuring reliable access to stored and managed persistent memories with privacy protection.

Instructions

Ping Qdrant Cloud and return connection status and latency.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of the health() method that pings Qdrant Cloud. Measures latency, tries /healthz endpoint first, falls back to collection check, and returns status ('healthy' or 'unavailable') with latencyMs.
    async health(): Promise<{
      status: "healthy" | "degraded" | "unavailable";
      latencyMs: number;
    }> {
      const start = Date.now();
      try {
        await qdrantRequest(qdrantUrl, qdrantApiKey, "GET", "/healthz");
        return { status: "healthy", latencyMs: Date.now() - start };
      } catch {
        // /healthz may not exist on all versions — try collections endpoint
        try {
          await qdrantRequest(qdrantUrl, qdrantApiKey, "GET", `/collections/${COLLECTION}`);
          return { status: "healthy", latencyMs: Date.now() - start };
        } catch {
          return { status: "unavailable", latencyMs: Date.now() - start };
        }
      }
    },
  • src/app.ts:249-257 (registration)
    Registration of the aiana_health tool in the tools array. Defines name, description, input schema (empty object), and execute function that delegates to adapter.health().
    {
      name: "aiana_health",
      description: "Ping Qdrant Cloud and return connection status and latency.",
      inputSchema: {
        type: "object",
        properties: {},
      },
      execute: async (_args) => adapter.health(),
    },
  • Type definition for the health() method return type in the AianaAdapter interface, specifying status as 'healthy' | 'degraded' | 'unavailable' and latencyMs as number.
    health(): Promise<{
      status: "healthy" | "degraded" | "unavailable";
      latencyMs: number;
    }>;
  • The qdrantRequest helper function used by health() to make HTTP requests to Qdrant. Handles authentication, error checking, and response parsing.
    async function qdrantRequest<T>(
      baseUrl: string,
      apiKey: string,
      method: string,
      path: string,
      body?: unknown,
    ): Promise<T> {
      const url = `${baseUrl}${path}`;
      const res = await fetch(url, {
        method,
        headers: makeQdrantHeaders(apiKey),
        body: body !== undefined ? JSON.stringify(body) : undefined,
      });
      if (!res.ok) {
        const text = await res.text().catch(() => "(no body)");
        throw new Error(`Qdrant ${method} ${path} → HTTP ${res.status}: ${text}`);
      }
      // DELETE 200 may return empty body
      const text = await res.text();
      if (!text) return {} as T;
      return JSON.parse(text) as T;
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the action (pinging) and the returned information (status and latency), which covers basic behavior. However, it lacks details on potential errors, timeouts, or side effects (e.g., if it affects the Qdrant Cloud service), leaving some behavioral aspects unclear.

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?

The description is a single, efficient sentence that directly states the tool's purpose and outcome without any redundant words. It is front-loaded with the core action and result, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate for basic understanding. However, it lacks details on output format (e.g., what 'status' includes) and error handling, which could be useful for an AI agent, making it minimally complete but with gaps.

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 has 0 parameters, and the schema description coverage is 100%, so no parameter documentation is needed. The description appropriately does not discuss parameters, earning a baseline score of 4 for this context, as it avoids unnecessary information.

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 clearly states the specific action ('Ping Qdrant Cloud') and the outcome ('return connection status and latency'), using precise verbs and specifying the target resource. It effectively distinguishes this tool from its siblings, which focus on memory operations, preferences, sessions, or status, by highlighting its diagnostic/connection-testing purpose.

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?

The description implies usage for checking Qdrant Cloud connectivity and latency, providing clear context for when to use it. However, it does not explicitly state when not to use it or name alternatives (e.g., other health-check tools), which prevents a score of 5.

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/git-fabric/aiana'

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