Skip to main content
Glama

provider_status

Checks the health of a specified TTS provider, or all configured providers when none is given, to verify availability before synthesis.

Instructions

Health-check one provider, or all configured providers when omitted.

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": "provider_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about whether the check is read-only, whether it performs live network calls, what happens on an unhealthy provider, or whether errors are returned versus reported in the payload. The only behavioral hint is the omission-means-all semantics, which is thin for an unannotated tool.

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?

One short sentence with the primary operation front-loaded and the default behavior attached to it. There is no filler wording and nothing important is buried.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the single optional parameter is covered. What is missing is a note on whether the check is safe/read-only and how failures surface, which matters for a diagnostic tool with no annotations at all.

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?

Schema description coverage is 0%, and the single `provider` parameter is nullable with a bare title, so the description is the only source of meaning. It successfully explains that supplying a provider narrows the check to one and omitting it targets all configured providers, which is the key semantic an agent needs.

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 gives a specific verb and resource ('health-check one provider') plus the scope split (single vs all). It does not name a sibling such as list_providers to contrast with, so an agent must infer that this checks status rather than enumerating configuration.

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?

It explicitly states the omission behavior ('all configured providers when omitted'), which is a usable invocation condition. However, it offers no guidance on when to prefer this over list_providers or synthesize, and no prerequisites or failure conditions are mentioned.

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

Deploy Server

Other Tools