Skip to main content
Glama

OutageDeck

by com.outagedeck

Watch a provider

watch_provider
Idempotent

Starts sending the caller outage alerts for one provider, either from the tracked catalog or from their own custom providers. Requires an API key. Alerts are emailed to the account address; the other channels (Slack, Teams, Discord, webhook) are set up on the account page, so no webhook URL ever has to be shared in a conversation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerYesA tracked provider (slug, name, or product name) or one of the caller's own custom providers.

TDQS

A4.2/5.0
Behavior4/5

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

Discloses authentication (API key) and delivery mechanism (email + account-page channels), adding context beyond the annotations. The annotations already declare idempotence and non-readonly; the description is consistent and adds operational detail.

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?

Three sentences, all earning their place: purpose, auth requirement, and channel setup. No wasted words.

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 simple one-param action, it covers the essential behavioral context. It does not describe the return value, but there is no output schema, so that is a minor gap.

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 schema covers 100% of parameters with a clear description of provider as slug/name/product or custom provider. The description mirrors this without adding extra syntax or format details.

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 'Starts sending outage alerts' which specifies the action and resource. It distinguishes from siblings like get_provider_status and get_outage_report by focusing on ongoing alerting rather than querying.

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?

Indicates the tool requires an API key and clarifies that alerts are emailed while other channels are configured on the account page. This gives practical context, but it does not explicitly name alternative tools or when-not conditions.

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

All OutageDeck toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct resource or action, and where overlap exists (e.g., search vs search_providers, fetch vs get_incident_details), descriptions clearly differentiate by entry point and use case.

Naming Consistency4/5

Most tools follow a verb_noun snake_case pattern (get_provider_status, list_active_incidents), but a few outliers like fetch, search, and check_my_stack deviate from the noun structure, though still readable.

Tool Count5/5

14 tools is within the ideal 3-15 range and covers the main functions of a status monitoring dashboard without unnecessary bloat.

Completeness4/5

The set covers searching, status checks, incident details, reliability reports, and custom provider CRUD. Missing unwatch/list watched providers are minor gaps but core workflows are supported.

Resources