Skip to main content
Glama

WhatsDownNow

Get service status

get_status
Read-onlyIdempotent

Current status of one service: verdict (up/degraded/down/unknown), plain-English summary, official status page level, our own HTTP probe, and user reports in the last hour. For AI API providers (OpenAI, Anthropic, Gemini, and others on /ai), also returns recommended_fallbacks — currently healthy alternatives you can switch to.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesService slug or common name, e.g. chatgpt (or 'openai'), claude (or 'anthropic'), aws, stripe. Use list_services to discover slugs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the description is not obliged to restate safety. It does add genuine behavioral context the annotations cannot: the freshness window of user reports (last hour), the conditional nature of recommended_fallbacks (only for AI API providers on /ai), and the notion of an own HTTP probe rather than just upstream status pages.

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, no filler, and the core purpose is front-loaded before the conditional AI-provider behavior. Every clause conveys a distinct fact an agent could act on.

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?

With no output schema, the description carries the burden of explaining return values, and it does so concretely (verdict enum values, summary, probe, reports, fallbacks). Minor gaps remain around unknown-slug behavior and whether results are cached, but nothing essential to calling the tool correctly is missing.

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 slug property already documents accepted formats (slug or common name, with chatgpt/openai and claude/anthropic examples) plus the list_services discovery hint. The description adds nothing about the parameter, so the baseline 3 for full schema coverage applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely (current status of one service) and enumerates the returned components: verdict, summary, status page level, HTTP probe, and user reports. That is far more specific than a tautology like 'gets service status.' It loses a point only because it does not distinguish itself from siblings such as get_ai_fallback, whose territory the recommended_fallbacks sentence partially overlaps.

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?

Usage is only implied: an agent can infer this is the tool for checking a single service's health. There is no explicit when-to-use statement, no exclusion (e.g., 'use list_services to browse' appears only in the schema, not the description), and no routing guidance toward get_ai_fallback or check_stack when the agent actually wants a fallback recommendation.

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.