Skip to main content
Glama

WhatsDownNow

Get a healthy AI provider fallback

get_ai_fallback
Read-onlyIdempotent

For AI API providers WhatsDownNow already tracks (OpenAI/ChatGPT, Anthropic/Claude, Gemini, Mistral, Groq, Perplexity, Cohere, xAI, DeepSeek, Together, Replicate, Hugging Face, OpenRouter, Fireworks), return currently healthy alternatives you can fail over to. Pass provider (slug or common name, e.g. 'openai' or 'chatgpt') for alternatives to one provider; omit it for the whole AI health board. Latency figures are from our HTTP probe of the public endpoint or status page, not model inference latency.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ai_fallback"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNoAI provider slug or name, e.g. chatgpt, openai, claude, anthropic. Omit to list every AI API we track.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds genuinely new context the annotations cannot carry: latency figures come from an HTTP probe of a public endpoint or status page, not model inference latency, which prevents a real misinterpretation of the returned data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and the provider/no-provider decision are front-loaded in the first two sentences, and the latency caveat is a well-placed qualifier. The parenthetical list of fifteen providers is long but earns its space by defining scope.

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?

For a single optional parameter with full schema coverage and explicit read-only annotations, the definition covers purpose, scope, and the latency caveat. It is slightly thin on what an 'alternative' record contains, though with no output schema that is a minor gap rather than a blocker.

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?

Schema description coverage is 100% and the schema already documents the provider slug/name with examples. The description restates the slug-or-common-name behavior and the omit semantics, which adds only marginal meaning beyond structured data, so the baseline 3 applies.

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 opens with a specific verb ('return') and resource ('currently healthy alternatives you can fail over to') scoped to AI API providers, and it enumerates the tracked providers so an agent knows coverage immediately. That distinguishes it from generic status tools like get_status or check_stack, which do not serve failover selection.

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?

It gives a clear decision rule: pass provider for alternatives to one provider, omit it for the whole AI health board. What's missing is any explicit routing against siblings (e.g., when to use get_status instead), so it is strong context without named exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.