sightline-webmcp.netlify.app
An incident war room a human and an AI agent investigate together, on the same screen, over WebMCP.
First seen 2026-11-05 · Last seen 2026-11-05 · Source: webmcp.com
Answer 2 · Act 6 · Transact 1 · Score: Not yet scored
Tool inspector
pin_finding
Add one evidence-backed conclusion to the shared incident timeline. This is the only way anything you work out reaches the on-call engineer: they are looking at the console, not at this conversation, so a conclusion you only state in your reply is one they never receive. Pin as you go, one finding per piece of evidence, rather than saving everything for a summary at the end. Write `evidence` so someone who did not watch you work can re-derive the claim. Critical findings are treated as root-cause claims by draft_incident_report. Side effect: creates a visible, attributed timeline entry.
Input schema
| Property | Type | Required | Description |
|---|---|---|---|
title |
string | yes | A one-line conclusion, up to 80 characters. |
evidence |
string | yes | Specific supporting observations, up to 500 characters. |
timestamp |
string | yes | Evidence time as HH:MM or a full ISO timestamp. |
severity |
string | yes | "info" for context, "warning" for a contributing factor or a ruled-out lead worth recording, "critical" for the causal finding. |
confidence |
number | no | Optional calibrated confidence from 0 to 1. Use 1 only when the evidence is conclusive. |
source_refs |
array | no | Tools whose results support this finding. These become jump links in the human timeline. |
Raw JSON schema
{
"type": "object",
"properties": {
"title": {
"type": "string",
"minLength": 1,
"maxLength": 80,
"description": "A one-line conclusion, up to 80 characters."
},
"evidence": {
"type": "string",
"minLength": 1,
"maxLength": 500,
"description": "Specific supporting observations, up to 500 characters."
},
"timestamp": {
"type": "string",
"minLength": 4,
"maxLength": 40,
"description": "Evidence time as HH:MM or a full ISO timestamp."
},
"severity": {
"type": "string",
"enum": [
"info",
"warning",
"critical"
],
"description": "\"info\" for context, \"warning\" for a contributing factor or a ruled-out lead worth recording, \"critical\" for the causal finding."
},
"confidence": {
"type": "number",
"minimum": 0,
"maximum": 1,
"description": "Optional calibrated confidence from 0 to 1. Use 1 only when the evidence is conclusive."
},
"source_refs": {
"type": "array",
"maxItems": 5,
"uniqueItems": true,
"items": {
"type": "string",
"enum": [
"get_service_health",
"query_metrics",
"filter_traces",
"search_logs",
"correlate_with_deploys"
]
},
"description": "Tools whose results support this finding. These become jump links in the human timeline."
}
},
"required": [
"title",
"evidence",
"timestamp",
"severity"
],
"additionalProperties": false
}
Similar websites
morphus.myles4miles.chatgpt.site
Morphus is an AI-native workspace for designing worlds and generating playable game experiences.
damnpdfs.com
Install the DamnPDFs Codex plugin, pair a browser workspace and use PDF, image and file tools from your coding agent. Includes setup and privacy limits.
insignifi4nt.github.io
broCAD/M: local-first CAD and CAM for parametric design, wire EDM planning, simulation and controller export.
cabinet.varera.studio
The Cartographer's Cabinet