Skip to main content
Glama

WhatsDownNow

List recent incidents

list_incidents
Read-onlyIdempotent

Recent incidents for a service: official incidents from its status page (when available) plus verdict changes WhatsDownNow detected.

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

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

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the description adds context beyond them by disclosing that results merge two sources and that status-page data is only present 'when available'. It says nothing about the time window implied by 'recent', result ordering, or volume, which are the real behavioral unknowns.

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?

One tight, front-loaded sentence with no filler. Its brevity is close to the minimum needed, though 'recent' is left unquantified.

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?

With no output schema, the description must convey return shape; it does so partially by naming the two entry types, but omits window size, ordering, and whether official and detected incidents are distinguishable in the response.

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?

A single required parameter with 100% schema description coverage, including examples and the cross-reference to list_services, so the schema already carries the semantics. The description adds no further meaning about slug resolution or aliases.

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?

Names the resource (incidents for a service) and specifies the two content sources: official status-page incidents and WhatsDownNow-detected verdict changes. This is more than a restatement of the title, though the verb is implied rather than stated and no sibling (e.g. get_status) is contrasted.

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 by 'for a service'; there is no explicit when-to-use statement, no guidance on choosing between this and get_status or check_stack, and no stated preconditions. The only routing hint (use list_services to discover slugs) lives in the schema rather than the description.

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.