Skip to main content
Glama

WhatsDownNow

List monitored services

list_services
Read-onlyIdempotent

List services WhatsDownNow monitors (slug, name, category). Optional filters: query (a name like 'openai' or 'google cloud'; returns the best matches) and category (AI, Developer & Cloud, Work & Productivity, Google, Microsoft, Apple, Social & Streaming, Money & Shopping, Gaming, Home & Security, Banks & Investing, Internet & Phone, Travel & Delivery). You rarely need this before create_alert_stack, which accepts common names directly.

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

Input Schema

NameRequiredDescriptionDefault
queryNoService name to look up, e.g. 'OpenAI', 'Cloudflare', 'Chase'
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds real behavior beyond that: that `query` does best-match lookup rather than exact matching, and that the catalog is a fixed set of categories. It stops short of noting result limits or whether an empty result is possible, which keeps it below a 5.

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

Conciseness3/5

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

The tool's actual guidance is front-loaded and tight, but the full 13-value category enumeration is copied verbatim from the input schema enum, spending a large share of the text on data the agent already receives. Trimming that list would lose nothing and roughly halve the description.

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?

There is no output schema, so stating the returned fields (slug, name, category) is load-bearing and correctly included. Combined with the 'you rarely need this' steering, an agent has enough to decide whether to call it. Only minor gaps remain — no mention of result count limits or ordering for the best-match query.

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 coverage is only 50% — `query` is documented in the schema but `category` has no description there. The description compensates by framing both as optional filters and by clarifying that `query` 'returns the best matches', a behavioral nuance the schema's 'Service name to look up' does not convey. The category value list is repeated verbatim from the enum rather than explaining filtering semantics, so the added meaning is partial.

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?

Opens with a specific verb+resource ('List services WhatsDownNow monitors') and immediately names the returned fields (slug, name, category). An agent can distinguish it from siblings like get_alert_stack or check_stack without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent it 'rarely need[s] this before create_alert_stack, which accepts common names directly' — a named alternative plus the condition that selects it. This is a genuine when-not-to-use rule, not just an implied context.

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.