Skip to main content
Glama

root_cause_candidates

Read-onlyIdempotent

Determine why an asset is failing by ranking root cause candidates from alerting dependencies, deepest first.

Instructions

Why is this asset failing? Alerting dependencies, most likely root cause first ('deepest' = nothing below it alerts).

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": {
      "asset": "<asset>"
    },
    "name": "root_cause_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds genuine behavior beyond that: results are alerting dependencies returned in root-cause-likelihood order, and 'deepest' is defined as having nothing below it that alerts, which tells the agent how to interpret the ranking.

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?

Two short sentences with the motivating question front-loaded and the ordering semantics clarified in a parenthetical. Nothing is wasted, though the phrasing is terse enough that 'alerting dependencies' requires context the reader may not have.

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 an output schema present, return values need not be explained, and for a one-parameter read-only tool the description covers the core semantic (ordering by root-cause likelihood). It stops short of stating traversal depth limits or expected result volume, which would matter for a graph-based diagnosis.

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?

Schema description coverage is 0%, so the description must carry the burden for the single 'asset' parameter, and it only implies it is the failing asset. It does not state whether the value is an ID, name, or path, which matters given a sibling like find_asset.

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?

The description frames the task as a diagnosis question ('Why is this asset failing?') and states the returned resource ('Alerting dependencies, most likely root cause first'), including an explicit definition of the 'deepest' ordering. It is not a bare restatement of the name, but it never names or contrasts a sibling such as impact_analysis, so differentiation is left to inference.

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?

The opening question implies the use case — diagnosing a failing asset — so an agent can infer when to reach for it. There is no explicit when-not guidance, no prerequisites, and no named alternative for related questions like blast radius, leaving usage context only implied.

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