Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_incident

Read a recovery-agent incident by id to get its trigger, classification, proposal, step-by-step narrative, pending approvals, outcome, and evidence. Use it to explain a failure the platform is already working.

Instructions

Read one recovery-agent incident by id — its trigger, classification, proposal, step-by-step narrative, approvals it is waiting on, outcome, and its evidence (before/after profile, diff, blast radius, thresholds, verdict). A pipeline incident's repair is regenerating the stored AI script; the evidence names the script versions before and after (scriptVersions), and revertToScriptVersions is what a failed verification restores. The one-line evidence summary of this evidence (numbers and column names, never values) is also what the incident webhook sends (evidenceSummary). When the operator asks about a failure the platform is already working, explain THIS record instead of re-diagnosing from scratch.

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": {
      "incident_id": "<incident_id>"
    },
    "name": "get_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
incident_idYesThe incident id (inc_…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose that this is a read of a single record, what a pipeline incident's repair actually is (regenerating the stored AI script), that revertToScriptVersions is what a failed verification restores, and that evidenceSummary carries numbers and column names but never values. However, it says nothing about behavior on an unknown or expired incident id, so the operational edge cases remain undocumented.

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?

Front-loaded with the verb and resource, then the return contents, then the usage rule — a sensible order. The middle sentence about script regeneration is dense but earns its place because it explains the scriptVersions and revertToScriptVersions fields an agent will encounter in the record.

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 has to describe the return value, and it does so thoroughly by enumerating record sections and the evidence sub-fields. The remaining gap is the unexplained boundary with the get_incident_evidence sibling, which leaves an agent unsure whether a narrower call exists.

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 coverage is 100% and the single parameter already documents the inc_… format, so the schema is doing the work. The phrase "by id" in the description adds no format, validation, or lookup semantics beyond what the schema states, which is the baseline expectation here.

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?

"Read one recovery-agent incident by id" names a specific verb and resource and then enumerates the record's contents (trigger, classification, proposal, narrative, approvals, outcome, evidence). It falls short of a 5 because the sibling get_incident_evidence overlaps with the evidence portion, and the description never says how the two divide the work.

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?

The final sentence gives a concrete usage rule with a named alternative behavior: when an operator asks about a failure the platform is already handling, explain THIS record rather than re-diagnosing. That is clear context without an explicit when-not list or a pointer to get_incident_evidence for callers who want only the evidence payload.

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

Deploy Server

Other Tools