Skip to main content
Glama

is_service_down

Check whether an AI service like Claude, OpenAI, or Gemini is currently down. Input the service name to get real-time status and identify outages or issues.

Instructions

Check if a specific AI service is currently down or experiencing issues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceYesService name to check (e.g. "claude", "openai", "gemini", "mistral", "cohere", "hugging face", "replicate")

Implementation Reference

  • The tool handler for 'is_service_down'. It fetches service status from the TensorFeed API, finds a matching service by name/provider, and returns its operational status.
    server.tool(
      'is_service_down',
      'Check if a specific AI service is currently down or experiencing issues.',
      {
        service: z.string().describe('Service name to check (e.g. "claude", "openai", "gemini", "mistral", "cohere", "hugging face", "replicate")'),
      },
      async ({ service }) => {
        const data = await fetchJSON('/status') as {
          services: { name: string; provider: string; status: string; components: { name: string; status: string }[] }[];
        };
    
        const match = data.services.find(s =>
          s.name.toLowerCase().includes(service.toLowerCase()) ||
          s.provider.toLowerCase().includes(service.toLowerCase())
        );
    
        if (!match) {
          return { content: [{ type: 'text' as const, text: `Service "${service}" not found. Available services: ${data.services.map(s => s.name).join(', ')}` }] };
        }
    
        const statusEmoji = match.status === 'operational' ? 'OK' : match.status === 'degraded' ? 'DEGRADED' : 'DOWN';
        const components = match.components.length > 0
          ? '\nComponents:\n' + match.components.map(c => `  ${c.name}: ${c.status}`).join('\n')
          : '';
    
        return {
          content: [{
            type: 'text' as const,
            text: `${statusEmoji} ${match.name} (${match.provider}) is ${match.status}${components}`
          }]
        };
      }
    );
  • The input schema for the 'is_service_down' tool, accepting a 'service' string parameter.
    {
      service: z.string().describe('Service name to check (e.g. "claude", "openai", "gemini", "mistral", "cohere", "hugging face", "replicate")'),
    },
  • Registration of the 'is_service_down' tool via the McpServer.tool() method.
    server.tool(
      'is_service_down',
      'Check if a specific AI service is currently down or experiencing issues.',
      {
        service: z.string().describe('Service name to check (e.g. "claude", "openai", "gemini", "mistral", "cohere", "hugging face", "replicate")'),
      },
      async ({ service }) => {
        const data = await fetchJSON('/status') as {
          services: { name: string; provider: string; status: string; components: { name: string; status: string }[] }[];
        };
    
        const match = data.services.find(s =>
          s.name.toLowerCase().includes(service.toLowerCase()) ||
          s.provider.toLowerCase().includes(service.toLowerCase())
        );
    
        if (!match) {
          return { content: [{ type: 'text' as const, text: `Service "${service}" not found. Available services: ${data.services.map(s => s.name).join(', ')}` }] };
        }
    
        const statusEmoji = match.status === 'operational' ? 'OK' : match.status === 'degraded' ? 'DEGRADED' : 'DOWN';
        const components = match.components.length > 0
          ? '\nComponents:\n' + match.components.map(c => `  ${c.name}: ${c.status}`).join('\n')
          : '';
    
        return {
          content: [{
            type: 'text' as const,
            text: `${statusEmoji} ${match.name} (${match.provider}) is ${match.status}${components}`
          }]
        };
      }
    );
  • The fetchJSON helper used by the tool to call the TensorFeed API endpoint.
    async function fetchJSON(path: string, opts: FetchOptions = {}): Promise<unknown> {
      const headers: Record<string, string> = {
        'User-Agent': `TensorFeed-MCP/${SDK_VERSION}`,
      };
      if (opts.body !== undefined) headers['Content-Type'] = 'application/json';
      if (opts.auth) {
        const token = process.env.TENSORFEED_TOKEN;
        if (!token) {
          throw new Error(
            'TENSORFEED_TOKEN env var is not set. Premium MCP tools require a bearer token. ' +
              'Buy credits at https://tensorfeed.ai/developers/agent-payments and pass the returned tf_live_... token via the TENSORFEED_TOKEN env var in your MCP client config.',
          );
        }
        headers['Authorization'] = `Bearer ${token}`;
      }
      const res = await fetch(`${API_BASE}${path}`, {
        method: opts.method ?? 'GET',
        headers,
        ...(opts.body !== undefined ? { body: JSON.stringify(opts.body) } : {}),
      });
      if (!res.ok) {
        let errPayload: unknown;
        try {
          errPayload = await res.json();
        } catch {
          errPayload = await res.text().catch(() => '');
        }
        if (res.status === 402) {
          throw new Error(
            `Payment required (402). Your token may be out of credits. Top up at https://tensorfeed.ai/developers/agent-payments. Detail: ${JSON.stringify(errPayload)}`,
          );
        }
        if (res.status === 401) {
          throw new Error(
            `Token rejected (401). Check that TENSORFEED_TOKEN is set to a valid tf_live_... token. Detail: ${JSON.stringify(errPayload)}`,
          );
        }
        throw new Error(`API error ${res.status}: ${JSON.stringify(errPayload)}`);
      }
      return res.json();
    }
Behavior2/5

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

No annotations are present, so the description carries full burden for behavioral disclosure. It does not describe how the check is performed, whether it's read-only, or what happens for unknown services. Only the basic purpose is mentioned.

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 sentence of 10 words, highly concise and front-loaded. Every word is necessary and contributes to understanding.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is too minimal. It does not specify the output format (e.g., boolean, status message) or any edge cases, leaving the agent without sufficient context for robust selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers 100% of the parameter with a description listing examples. The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 uses a specific verb 'check' and identifies the resource as 'specific AI service', clearly stating the tool's function. It is unambiguous and distinguishes it from potential siblings by focusing on current downtime status.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_ai_status' or 'status_uptime'. The description does not include context, exclusions, or prerequisites for usage.

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/RipperMercs/tensorfeed'

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