Operations example

Find the incident before the alert storm

“Which production services are unhealthy in us-east?”

get_service_health

The browser finds one tool on the website. The tool sends one request to the existing API.

User request

Which production services are unhealthy in us-east?

Browser tool call

Code
get_service_health({
  "environment": "production",
  "region": "us-east"
})

OpenAPI setting

JSON
{
  "operationId": "get_service_health",
  "description": "List service health for one environment and region.",
  "x-webmcp-enabled": true,
  "parameters": [
    {
      "name": "environment",
      "in": "query",
      "required": true,
      "schema": {
        "type": "string",
        "enum": [
          "staging",
          "production"
        ]
      }
    },
    {
      "name": "region",
      "in": "query",
      "required": true,
      "schema": {
        "type": "string"
      }
    }
  ]
}

Existing API request

Code
GET /api/services/health?environment=production&region=us-east

Why this is a fit

This request only reads data. It uses simple values in the path or query. The website can check the current user’s access before the API returns data.

What stays out

The tool cannot change data. It does not create incidents, change inventory, update tickets, or edit metrics.

All examples

Start typing to search.