← WebMCP Directory

Tool tree

nexusops-nu.vercel.app

Developer ToolsTools verified
Website
A WebMCP-powered IT operations platform for investigating production incidents with AI agent collaboration
Explore capabilities
    get_active_incidentsAnswer

    List active production incidents requiring operator attention. Call this first to discover what is currently broken before investigating a specific incident. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "get_active_incidents",
      "kind": "answer",
      "impl": "imperative",
      "description": "List active production incidents requiring operator attention. Call this first to discover what is currently broken before investigating a specific incident. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {},
        "required": [],
        "additionalProperties": false
      }
    }
    get_incidentAnswer

    Retrieve the current state of a specific incident: severity, status, affected service and symptoms. Use this to confirm incident details before further investigation. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "get_incident",
      "kind": "answer",
      "impl": "imperative",
      "description": "Retrieve the current state of a specific incident: severity, status, affected service and symptoms. Use this to confirm incident details before further investigation. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "incident_id": {
            "type": "string",
            "description": "Incident identifier, for example INC-1042."
          }
        },
        "required": [
          "incident_id"
        ],
        "additionalProperties": false
      }
    }
    get_servicesAnswer

    List all services and their current health status. Use this to see the broader service landscape and confirm which services are healthy vs. degraded. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "get_services",
      "kind": "answer",
      "impl": "imperative",
      "description": "List all services and their current health status. Use this to see the broader service landscape and confirm which services are healthy vs. degraded. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {},
        "required": [],
        "additionalProperties": false
      }
    }
    get_incident_evidenceAnswer

    Return the consolidated metrics, logs, timeline, deployment and prior-finding evidence already gathered for an incident in one call. Use this to get a single evidence snapshot instead of calling multiple observation tools individually. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "get_incident_evidence",
      "kind": "answer",
      "impl": "imperative",
      "description": "Return the consolidated metrics, logs, timeline, deployment and prior-finding evidence already gathered for an incident in one call. Use this to get a single evidence snapshot instead of calling multiple observation tools individually. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "incident_id": {
            "type": "string",
            "description": "Incident identifier, for example INC-1042."
          }
        },
        "required": [
          "incident_id"
        ],
        "additionalProperties": false
      }
    }
    get_service_healthAnswer

    Retrieve a service's current health signals: status, latency, error rate, request rate, CPU and memory. Use this to quickly assess whether a service is under resource pressure. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "get_service_health",
      "kind": "answer",
      "impl": "imperative",
      "description": "Retrieve a service's current health signals: status, latency, error rate, request rate, CPU and memory. Use this to quickly assess whether a service is under resource pressure. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "service_id": {
            "type": "string",
            "description": "Service identifier, for example payment-api."
          }
        },
        "required": [
          "service_id"
        ],
        "additionalProperties": false
      }
    }
    get_dependenciesAnswer

    Retrieve a service's dependency graph and the health of each dependency. Use this to check whether a failure is isolated to one service or part of a broader dependency chain. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "get_dependencies",
      "kind": "answer",
      "impl": "imperative",
      "description": "Retrieve a service's dependency graph and the health of each dependency. Use this to check whether a failure is isolated to one service or part of a broader dependency chain. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "service_id": {
            "type": "string",
            "description": "Service identifier, for example payment-api."
          }
        },
        "required": [
          "service_id"
        ],
        "additionalProperties": false
      }
    }
    get_deployment_historyAnswer

    Retrieve recent deployments for a service, including what changed and when. Use this to check whether a recent release could explain a regression. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "get_deployment_history",
      "kind": "answer",
      "impl": "imperative",
      "description": "Retrieve recent deployments for a service, including what changed and when. Use this to check whether a recent release could explain a regression. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "service_id": {
            "type": "string",
            "description": "Service identifier, for example payment-api."
          }
        },
        "required": [
          "service_id"
        ],
        "additionalProperties": false
      }
    }
    get_metricsAnswer

    Retrieve a time series of a service's telemetry: latency, request rate, error rate, CPU, memory and database connections. Use this to quantify how severe a degradation is. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "get_metrics",
      "kind": "answer",
      "impl": "imperative",
      "description": "Retrieve a time series of a service's telemetry: latency, request rate, error rate, CPU, memory and database connections. Use this to quantify how severe a degradation is. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "service_id": {
            "type": "string",
            "description": "Service identifier, for example payment-api."
          }
        },
        "required": [
          "service_id"
        ],
        "additionalProperties": false
      }
    }
    get_logsAnswer

    Retrieve structured application logs for a service. Use this to find the specific error or timeout events that explain elevated metrics. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "get_logs",
      "kind": "answer",
      "impl": "imperative",
      "description": "Retrieve structured application logs for a service. Use this to find the specific error or timeout events that explain elevated metrics. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "service_id": {
            "type": "string",
            "description": "Service identifier, for example payment-api."
          }
        },
        "required": [
          "service_id"
        ],
        "additionalProperties": false
      }
    }
    get_incident_timelineAnswer

    Retrieve the chronological sequence of events leading up to an incident. Use this to establish whether a deployment or other change preceded the incident. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "get_incident_timeline",
      "kind": "answer",
      "impl": "imperative",
      "description": "Retrieve the chronological sequence of events leading up to an incident. Use this to establish whether a deployment or other change preceded the incident. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "incident_id": {
            "type": "string",
            "description": "Incident identifier, for example INC-1042."
          }
        },
        "required": [
          "incident_id"
        ],
        "additionalProperties": false
      }
    }
    compare_metricsAnswer

    Compare an incident's current telemetry against its prior healthy baseline and return the delta for each metric. Use this to measure how far a service has drifted from normal. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "compare_metrics",
      "kind": "answer",
      "impl": "imperative",
      "description": "Compare an incident's current telemetry against its prior healthy baseline and return the delta for each metric. Use this to measure how far a service has drifted from normal. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "incident_id": {
            "type": "string",
            "description": "Incident identifier."
          },
          "service_id": {
            "type": "string",
            "description": "Service identifier."
          }
        },
        "required": [
          "incident_id",
          "service_id"
        ],
        "additionalProperties": false
      }
    }
    correlate_eventsAnswer

    Cross-reference deployment events, telemetry changes, log signals and incident timing into one correlation summary. Use this after gathering individual evidence to look for a consistent causal pattern. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "correlate_events",
      "kind": "answer",
      "impl": "imperative",
      "description": "Cross-reference deployment events, telemetry changes, log signals and incident timing into one correlation summary. Use this after gathering individual evidence to look for a consistent causal pattern. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "incident_id": {
            "type": "string",
            "description": "Incident identifier."
          },
          "service_id": {
            "type": "string",
            "description": "Service identifier."
          }
        },
        "required": [
          "incident_id",
          "service_id"
        ],
        "additionalProperties": false
      }
    }
    run_diagnosticAnswer

    Run a structured diagnostic comparing a service's current telemetry, deployments and logs against baseline, returning a diagnosis, confidence and recommended next step. Use this as a final cross-check before proposing remediation. Read-only: it never executes remediation.

    View tool JSON
    {
      "name": "run_diagnostic",
      "kind": "answer",
      "impl": "imperative",
      "description": "Run a structured diagnostic comparing a service's current telemetry, deployments and logs against baseline, returning a diagnosis, confidence and recommended next step. Use this as a final cross-check before proposing remediation. Read-only: it never executes remediation.",
      "inputSchema": {
        "type": "object",
        "properties": {},
        "required": [],
        "additionalProperties": false
      }
    }
    create_investigation_findingAction

    Store a human-readable investigation finding for operator review. Use this to persist a conclusion so a human can audit how it was reached. Mutating but low-risk: it only appends to the investigation record and cannot affect production.

    View tool JSON
    {
      "name": "create_investigation_finding",
      "kind": "act",
      "impl": "imperative",
      "description": "Store a human-readable investigation finding for operator review. Use this to persist a conclusion so a human can audit how it was reached. Mutating but low-risk: it only appends to the investigation record and cannot affect production.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "incident_id": {
            "type": "string",
            "description": "Incident identifier."
          },
          "finding": {
            "type": "string",
            "description": "Investigation finding to store for operator review."
          }
        },
        "required": [
          "incident_id",
          "finding"
        ],
        "additionalProperties": false
      }
    }
    propose_remediationAction

    Generate a specific, evidence-based mitigation recommendation (target action, rationale, risk) for a human to review. Use this once a root cause is established. Read-only: it proposes an action but never executes anything and always requires human approval first.

    View tool JSON
    {
      "name": "propose_remediation",
      "kind": "act",
      "impl": "imperative",
      "description": "Generate a specific, evidence-based mitigation recommendation (target action, rationale, risk) for a human to review. Use this once a root cause is established. Read-only: it proposes an action but never executes anything and always requires human approval first.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "incident_id": {
            "type": "string",
            "description": "Incident identifier, for example INC-1042."
          }
        },
        "required": [
          "incident_id"
        ],
        "additionalProperties": false
      }
    }
    approve_remediationAction

    Record an explicit human operator approval for a specific remediation action on a specific incident. This tool represents a human decision, not an agent decision, and is the only way execute_remediation can subsequently succeed.

    View tool JSON
    {
      "name": "approve_remediation",
      "kind": "act",
      "impl": "imperative",
      "description": "Record an explicit human operator approval for a specific remediation action on a specific incident. This tool represents a human decision, not an agent decision, and is the only way execute_remediation can subsequently succeed.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "incident_id": {
            "type": "string"
          },
          "action": {
            "type": "string",
            "enum": [
              "rollback_payment_api"
            ]
          }
        },
        "required": [
          "incident_id",
          "action"
        ],
        "additionalProperties": false
      }
    }
    execute_remediationAction

    Execute a previously proposed, simulated remediation action (e.g. a rollback). Mutating and high-risk: this call is rejected unless a matching approve_remediation call was already recorded for the same incident and action. Never call this without confirmed human approval.

    View tool JSON
    {
      "name": "execute_remediation",
      "kind": "act",
      "impl": "imperative",
      "description": "Execute a previously proposed, simulated remediation action (e.g. a rollback). Mutating and high-risk: this call is rejected unless a matching approve_remediation call was already recorded for the same incident and action. Never call this without confirmed human approval.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "incident_id": {
            "type": "string"
          },
          "action": {
            "type": "string",
            "enum": [
              "rollback_payment_api"
            ]
          },
          "approved": {
            "type": "boolean",
            "description": "Must be true and must match recorded human approval."
          }
        },
        "required": [
          "incident_id",
          "action",
          "approved"
        ],
        "additionalProperties": false
      }
    }
    verify_remediationAnswer

    Verify whether a service has actually recovered after remediation, based on its real current status and metrics. Use this after execute_remediation; it reports no recovery if remediation hasn't run yet. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "verify_remediation",
      "kind": "answer",
      "impl": "imperative",
      "description": "Verify whether a service has actually recovered after remediation, based on its real current status and metrics. Use this after execute_remediation; it reports no recovery if remediation hasn't run yet. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "incident_id": {
            "type": "string",
            "description": "Incident identifier, for example INC-1042."
          }
        },
        "required": [
          "incident_id"
        ],
        "additionalProperties": false
      }
    }
    verify_incidentAnswer

    Verify the current state of an incident (open vs. resolved) based on real service status. Use this to check overall incident closure independent of any specific remediation. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "verify_incident",
      "kind": "answer",
      "impl": "imperative",
      "description": "Verify the current state of an incident (open vs. resolved) based on real service status. Use this to check overall incident closure independent of any specific remediation. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "incident_id": {
            "type": "string",
            "description": "Incident identifier, for example INC-1042."
          }
        },
        "required": [
          "incident_id"
        ],
        "additionalProperties": false
      }
    }
    get_agent_activityAnswer

    Read the live audit trail of every tool invocation made so far: agent, tool, arguments, duration and success. Use this to review what has already been investigated or executed before duplicating work. Read-only; safe to call at any time.

    View tool JSON
    {
      "name": "get_agent_activity",
      "kind": "answer",
      "impl": "imperative",
      "description": "Read the live audit trail of every tool invocation made so far: agent, tool, arguments, duration and success. Use this to review what has already been investigated or executed before duplicating work. Read-only; safe to call at any time.",
      "inputSchema": {
        "type": "object",
        "properties": {},
        "required": [],
        "additionalProperties": false
      }
    }