Skip to main content
Glama

get_api_status

Check Carbone API health and version to verify connectivity and identify the active API version.

Instructions

Check Carbone API health and version. Returns the current API version and a status message. Useful for verifying connectivity and confirming which Carbone version is active.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the get_api_status tool. Calls client.getStatus() and returns the API version and message as text content.
    export async function handleGetApiStatus(client: CarboneClient, options?: CallOptions) {
      try {
        const status = await client.getStatus(options);
        return {
          content: [
            {
              type: 'text' as const,
              text: `Carbone API: online (v${status.version})\nMessage: ${status.message}`,
            },
          ],
        };
      } catch (error) {
        return { content: [{ type: 'text' as const, text: formatError(error) }], isError: true };
      }
    }
  • Schema definition for get_api_status — an empty schema {} since no input parameters are required.
    export const getApiStatusSchema = {};
  • Registration of the get_api_status tool with the MCP server. Uses getApiStatusToolName, description, and binds handleGetApiStatus with the client.
    server.registerTool(
      getApiStatusToolName,
      { description: getApiStatusDescription },
      (extra) => handleGetApiStatus(client, { apiKey: extra.authInfo?.token })
    );
  • Client method getStatus() that makes the actual HTTP GET /status request to the Carbone API and returns ApiStatus (version, message).
    async getStatus(options?: CallOptions): Promise<ApiStatus> {
      const response = await this.request('/status', { method: 'GET' }, { ...options, skipAuthCheck: true });
      const json = await response.json() as { version: string; message: string };
      return { version: json.version, message: json.message };
    }
  • Type definition for ApiStatus containing version (string) and message (string) fields.
    export interface ApiStatus {
      version: string;
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that the tool returns version and status, implying a safe read operation. Could mention authentication or rate limits, but for a health check it's sufficient.

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 sentences, front-loaded with the main action and return info. 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 parameterless tool with no output schema, the description fully covers purpose, return value, and usage context. No 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?

No parameters, baseline 4. Description adds no parameter info, but schema coverage is 100% (empty), so no further detail needed.

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 it checks Carbone API health and version, returning version and status. This is distinct from all sibling tools, which deal with document conversion, templates, etc.

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?

Explicitly says 'useful for verifying connectivity and confirming which Carbone version is active', providing clear context. No when-not or alternatives needed due to simplicity.

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/carboneio/carbone-mcp'

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