Skip to main content
Glama
AlephantAI

Alephant MCP

Official
by AlephantAI

check_alephant_connection

Read-onlyIdempotent

Check if Alephant API is reachable and credentials are valid for the current MCP configuration.

Instructions

Checks Alephant API connectivity and credential usability for the current MCP mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The registerConnectionHealthTool function registers the 'check_alephant_connection' tool. In vk mode, it calls cockpit.health() (public endpoint). In manager mode, it calls manager.getWorkspaceOverview() and includes the workspace ID.
    export function registerConnectionHealthTool(server: McpServer, deps: ToolDeps): void {
      server.tool(
        "check_alephant_connection",
        "Checks Alephant API connectivity and credential usability for the current MCP mode.",
        {},
        async () => {
          if (deps.mode === "vk") {
            const cockpit = requireCockpit(deps);
            return safeCall(async () => ({
              mode: "vk",
              status: "ok",
              health: await cockpit.health(),
            }), deps.mode);
          }
    
          const manager = requireManager(deps);
          return safeCall(async () => ({
            mode: "manager",
            status: "ok",
            workspaceId: manager.getWorkspaceId(),
            overview: await manager.getWorkspaceOverview(),
          }), deps.mode);
        },
      );
    }
  • The tool has an empty schema ({}) — no input parameters required.
    {},
  • Description metadata mapping for 'check_alephant_connection' used during marketplace registration.
    check_alephant_connection:
      "Checks Alephant API connectivity and credential usability for the current MCP mode.",
  • registerConnectionHealthTool is called in registerTools(), registering the tool on the MCP server for both vk and manager modes.
    registerConnectionHealthTool(server, deps);
  • requireCockpit and requireManager helper functions used by the tool handler to access the appropriate API client.
    export function requireCockpit(deps: ToolDeps): CockpitClient {
      if (!deps.cockpit) throw new Error("Cockpit client not configured");
      return deps.cockpit;
    }
    
    export function requireManager(deps: ToolDeps): ManagerClient {
      if (!deps.manager) throw new Error("Manager client not configured");
      return deps.manager;
    }
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by specifying that it checks connectivity and credential usability for the current MCP mode, providing context beyond annotations.

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, clear sentence that efficiently conveys the purpose with no wasted words.

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?

Given the tool's simplicity (no parameters, no output schema) and the annotations, the description is sufficient. It covers the core purpose, though additional detail on what exactly is checked or the response could enhance completeness.

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 zero parameters, so the description need not add parameter information. Baseline score of 4 applies as it adds no unnecessary detail.

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 tool checks Alephant API connectivity and credential usability, using a specific verb and resource. It distinguishes from sibling tools that focus on costs, models, etc.

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

Usage Guidelines3/5

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

The description does not explicitly say when to use this tool versus alternatives, but implies it is for verifying connectivity before other operations. No exclusions or alternatives are mentioned.

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/AlephantAI/alephant-mcp'

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