Skip to main content
Glama

WhatsDownNow

Report an error you hit

report_issue

Tell WhatsDownNow that your agent or app hit an error talking to a tracked service. Use this when you see 5xx, timeouts, or rate limits, even if our status page still says up — several independent reports in a short window are flagged as an agent-reported spike. Fields: service (slug or name), error_type (5xx, timeout, rate_limit, auth, network, other), optional model and region. Rate-limited and deduplicated per network. Also counts toward user-report alert thresholds.

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": {
      "service": "<service>",
      "error_type": "<error_type>"
    },
    "name": "report_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoModel id if known, e.g. gpt-4.1 or claude-sonnet-4
detailNoOptional short note (no secrets or personal data)
regionNoRegion or endpoint if known, e.g. us-east-1
serviceYesService slug or common name, e.g. chatgpt, anthropic, aws
error_typeYesWhat you observed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, it discloses that submissions are rate-limited and deduplicated per network, that multiple independent reports in a short window are clustered into an agent-reported spike, and that reporting feeds user-report alert thresholds. Those are exactly the consequences an agent cannot infer from readOnlyHint=false and destructiveHint=false.

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?

Purpose and trigger conditions are front-loaded in the first two sentences, and the operational effects follow in a compact third. Every clause carries information, though the trailing note about user-report alert thresholds is the least essential and slightly dilutes the close.

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 still conveys what happens to a submitted report (deduplication, spike flagging, threshold contribution), which is the behavior an agent needs before filing repeatedly. It does not describe the confirmation or response the caller receives, which is a minor remaining 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 description restates the fields already documented at 100% schema coverage: service, error_type with its enum values, plus optional model and region. It adds no format or constraint detail (for example how service slugs resolve) beyond what the schema already provides, so the high-coverage baseline of 3 applies.

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 opening sentence names a specific verb and resource: tell WhatsDownNow that an agent or app hit an error against a tracked service. The trigger list (5xx, timeouts, rate limits) further pins the resource to runtime errors rather than service status, which separates it from siblings like get_status or check_stack.

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?

It gives an explicit when-to-use condition — you are seeing 5xx, timeouts, or rate limits — and notably says to report even when the status page still says up, which preempts the obvious alternative action. No sibling tool is named as an alternative for other cases, so it stops just short of a full routing statement.

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.