Skip to main content
Glama

what_is_broken

Reports current system status, monitoring coverage, and open incidents with service, age, owner, failure, likely cause, and next step. Use it to see whether anything needs attention.

Instructions

What is wrong right now, as the AI SRE home page says it: the headline, whether anybody is watching the services and, if not, why and since when, and every open incident with its service, how long it has been open, who is on it, what is failing, the likely cause and the next step. Start here when the person asks what is broken, what is on fire or whether anything needs them.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does so well: it discloses that the result covers watch status, open-incident ages and ownership, plus diagnosis fields. It implicitly reads as a read-only summary, but it does not state freshness/as-of semantics or limits on how many incidents are returned — minor gaps for a zero-parameter query 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?

Two sentences, front-loaded with the core question and then the payload it returns, followed by a routing sentence. The list of incident fields is long but each item helps an agent decide whether this is the right first call; nothing is redundant.

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

Completeness5/5

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

With zero parameters and an output schema present, the description only needs to convey purpose, trigger and scope — all three are covered. An agent knows exactly when to reach for this and roughly what comes back without opening the schema.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly implies no input is required by framing it as a standing question ('what is wrong right now') rather than a filtered query.

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 names the resource and its scope precisely — the SRE headline, whether services are being watched (and why not), and every open incident with service, age, owner, failing component, likely cause and next step. This enumerates concrete outputs, which separates it from per-project/per-service siblings like how_is_project and how_is_service.

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 states an explicit entry condition: 'Start here when the person asks what is broken, what is on fire or whether anything needs them.' That is a clear use trigger, though it stops short of naming a sibling as the alternative or saying when not to start here (e.g. when the ask is scoped to one project or service).

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