Skip to main content
Glama

Devops Status Check

devops_status_check
Read-onlyIdempotent

Check the current health status for one or more vendors. Accepts registered vendor slugs (e.g., "github", "aws", "gcp", "gitlab") or raw Atlassian Statuspage base URLs. Registry entries are served by each vendor's native status API (Statuspage, Status.io, Slack, AWS Health, Google Cloud Service Health, Azure status, Azure DevOps status, Firehydrant, Datadog) and normalized to one shape. Returns per-vendor operational indicator as the vendor published it (none = no degradation reported, minor, major, critical, maintenance = scheduled window), degraded components, and active incidents; summary counts each vendor at the worse of its indicator and its worst open incident rated minor or worse. Use mode: "detailed" for component lists and maintenance windows, narrowed with component_filter, bounded by component_limit, and paged with component_offset. Batch-friendly — pass a list to check your full stack in one call; up to 20 vendors are checked per call, and any past the 20th come back in deferred_vendors to resend. A vendor that cannot be resolved or reached is reported in its own result row, so one bad entry never discards the rest. Every vendor with an active problem gets a pre-filled devops_suggest_action call in nextToolSuggestions.

Input Schema

NameRequiredDescriptionDefault
modeNosummary: indicator + degraded components + active incidents only. detailed: adds the component list and scheduled maintenance windows.summary
vendorsYesVendor slugs from the built-in registry (e.g., "github", "aws") or raw Atlassian Statuspage base URLs (non-Statuspage backends are supported via registry slugs only). Mix freely. Use devops_list_vendors to discover available slugs. The first 20 are checked, in the order given; entries past the 20th are returned unchecked in deferred_vendors to resend in another call. Lists longer than 100 are rejected.
component_limitNoMaximum components returned per vendor in detailed mode, at least 1. A value above 500 is reduced to 500, and notice says so; a longer list continues with component_offset. Large status pages publish hundreds of components, so a multi-vendor batch at a high limit returns a very large response; narrow with component_filter instead where possible.
component_filterNoCase-insensitive substring matched against component names and their group names in detailed mode (e.g., "api" to check just the API components, or a product or region a page groups components under). Applied before component_offset and component_limit, so it reaches a specific component without paging, and an offset pages within the filtered list. A filter that matches nothing for a vendor is reported in notice. Ignored in summary mode.
component_offsetNoComponents to skip per vendor, after component_filter and before component_limit. Pass a vendor's next_component_offset to continue its list. An offset past a vendor's last component returns an empty list for it, and notice says so. Ignored in summary mode.

Output Schema

NameRequiredDescriptionDefault
capNoThe per-vendor component_limit that was applied. Present only when truncated.
errorNoPresent when the call failed. Absent on success.
shownNoComponents returned across all vendors. Present only when truncated.
noticeNoPlain-language explanation of what this call left out or adjusted, in this order: vendors past the first 20 (listed in deferred_vendors); a component_limit above 500 reduced to 500; in detailed mode, how many components lie past the returned page and how to reach them (this tool again with that vendor and its next_component_offset as component_offset, component_filter to target one, or component_limit to raise a cap below 500), which vendors component_offset ran past the end of, and which checked vendors component_filter matched no component of, with how many each publishes; and last, for a vendor whose entry reads an umbrella status page with no components (atlassian), the slugs of the entries reading its product pages. Present only when one of these applies.
resultsNoPer-vendor status results for the vendors checked, in the same order as the input vendors list.
summaryNoAggregate health counts across all checked vendors. Each vendor is rated by the worse of its indicator and its worst open incident rated minor or worse; an incident rated none or maintenance never raises the rating. Buckets partition the batch: operational + degraded + down + maintenance + unavailable = total.
truncatedNoTrue when at least one vendor has components past the returned page — those vendors carry next_component_offset. Absent otherwise, including on the last page of a list.
totalCountNoComponents matching component_filter across all vendors, before component_offset and the cap. Present only when truncated.
deferred_vendorsNoEntries past the first 20 in vendors, verbatim and in input order. They were not checked; resend them in another call. Empty when every entry was checked.
nextToolSuggestionsNoOne devops_suggest_action call per vendor with an active problem — an indicator of minor, major, or critical, or an open incident of that impact even while the indicator reads none or maintenance; these are the vendors summary counts as degraded or down — with its arguments filled from that vendor's result. Vendors that could not be checked never appear. Empty when no checked vendor has an active problem.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • changedInput schema / properties / component_filter / description
      Previous value: -"Case-insensitive substring matched against component names and their group names in detailed mode (e.g., \"api\" to check just the API components, or a product or region a page groups components under). Applied before component_limit, so it is the way to reach a component that the cap would otherwise omit. A filter that matches nothing for a vendor is reported in notice. Ignored in summary mode."New value: +"Case-insensitive substring matched against component names and their group names in detailed mode (e.g., \"api\" to check just the API components, or a product or region a page groups components under). Applied before component_offset and component_limit, so it reaches a specific component without paging, and an offset pages within the filtered list. A filter that matches nothing for a vendor is reported in notice. Ignored in summary mode."
    • changedInput schema / properties / component_limit / description
      Previous value: -"Maximum components returned per vendor in detailed mode, at least 1. A value above 500 is reduced to 500, and notice says so. Large status pages publish hundreds of components, so a multi-vendor batch at a high limit returns a very large response; narrow with component_filter instead where possible."New value: +"Maximum components returned per vendor in detailed mode, at least 1. A value above 500 is reduced to 500, and notice says so; a longer list continues with component_offset. Large status pages publish hundreds of components, so a multi-vendor batch at a high limit returns a very large response; narrow with component_filter instead where possible."
    • addedInput schema / properties / component_offset
      Added value: +{
      +  "default": 0,
      +  "description": "Components to skip per vendor, after component_filter and before component_limit. Pass a vendor's next_component_offset to continue its list. An offset past a vendor's last component returns an empty list for it, and notice says so. Ignored in summary mode.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedOutput schema / properties / nextToolSuggestions / description
      Previous value: -"One devops_suggest_action call per vendor with an active problem — an indicator of minor, major, or critical, or an open incident of that impact even while the indicator reads none or maintenance — with its arguments filled from that vendor's result. Vendors that could not be checked never appear. Empty when no checked vendor has an active problem."New value: +"One devops_suggest_action call per vendor with an active problem — an indicator of minor, major, or critical, or an open incident of that impact even while the indicator reads none or maintenance; these are the vendors summary counts as degraded or down — with its arguments filled from that vendor's result. Vendors that could not be checked never appear. Empty when no checked vendor has an active problem."
    • changedOutput schema / properties / notice / description
      Previous value: -"Plain-language explanation of what this call left out or adjusted: vendors past the first 20 (listed in deferred_vendors), a component_limit above 500 reduced to 500, and in detailed mode how many components the cap omitted and how to reach them (component_filter to target one, or component_limit to raise a cap below 500), and which checked vendors component_filter matched no component of, with how many each publishes. Present only when one of these applies."New value: +"Plain-language explanation of what this call left out or adjusted, in this order: vendors past the first 20 (listed in deferred_vendors); a component_limit above 500 reduced to 500; in detailed mode, how many components lie past the returned page and how to reach them (this tool again with that vendor and its next_component_offset as component_offset, component_filter to target one, or component_limit to raise a cap below 500), which vendors component_offset ran past the end of, and which checked vendors component_filter matched no component of, with how many each publishes; and last, for a vendor whose entry reads an umbrella status page with no components (atlassian), the slugs of the entries reading its product pages. Present only when one of these applies."
    • changedOutput schema / properties / results / items / properties / all_components / description
      Previous value: -"Components including operational ones, capped at component_limit per vendor and narrowed by component_filter (matched against name and group) when given. Present in detailed mode only."New value: +"Components including operational ones, narrowed by component_filter (matched against name and group) when given, starting at component_offset (devops_status_check only; the first component otherwise), and at most component_limit per vendor. Present in detailed mode only."
    • changedOutput schema / properties / results / items / properties / all_components_total / description
      Previous value: -"Components matching component_filter for this vendor before the component_limit cap. Larger than the length of all_components when this vendor was capped. Present in detailed mode only."New value: +"Components matching component_filter for this vendor, before component_offset and component_limit — the length of the whole list all_components is a page of. Present in detailed mode only."
    • changedOutput schema / properties / results / items / properties / cached / description
      Previous value: -"True when this result was served from the 60s in-memory cache."New value: +"True when this result was served from the in-memory status cache, shared across callers (60 s TTL by default), so its data can be up to that TTL older than checked_at."
    • changedOutput schema / properties / results / items / properties / checked_at / description
      Previous value: -"ISO 8601 UTC timestamp of this check."New value: +"ISO 8601 UTC timestamp of this check — when this result was built, not when the status data was fetched; see cached."
    • changedOutput schema / properties / results / items / properties / indicator / description
      Previous value: -"Overall health indicator: none = all clear, minor = some degradation, major = significant outage, critical = complete outage, maintenance = scheduled window in progress, planned rather than a fault."New value: +"Overall health indicator, as the vendor published it: none = no degradation reported, minor = some degradation, major = significant outage, critical = complete outage, maintenance = scheduled window in progress, planned rather than a fault. A page can rate it from component statuses alone, so it can read none or maintenance while active_incidents lists an open incident rated minor or worse; summary, and devops_watch_stack's health, rate the vendor by the worse of the two."
    • addedOutput schema / properties / results / items / properties / next_component_offset
      Added value: +{
      +  "description": "Where this vendor's component list continues. Present in detailed mode only, and only when components remain past the returned page: pass it as component_offset to devops_status_check, with this vendor, mode \"detailed\", and the same component_filter. Absent on the last page.",
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
    • changedOutput schema / properties / results / items / properties / scheduled_maintenances / items / properties / scheduled_until / description
      Previous value: -"ISO 8601 end time, with the vendor's UTC offset."New value: +"ISO 8601 end time, with the vendor's UTC offset, or null when the vendor's feed publishes no planned end."
    • changedOutput schema / properties / results / items / properties / scheduled_maintenances / items / properties / scheduled_until / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / summary / description
      Previous value: -"Aggregate health counts across all checked vendors. Buckets partition the batch: operational + degraded + down + maintenance + unavailable = total."New value: +"Aggregate health counts across all checked vendors. Each vendor is rated by the worse of its indicator and its worst open incident rated minor or worse; an incident rated none or maintenance never raises the rating. Buckets partition the batch: operational + degraded + down + maintenance + unavailable = total."
    • changedOutput schema / properties / summary / properties / degraded / description
      Previous value: -"Vendors with indicator = minor or major."New value: +"Vendors rated minor or major."
    • changedOutput schema / properties / summary / properties / down / description
      Previous value: -"Vendors with indicator = critical."New value: +"Vendors rated critical."
    • changedOutput schema / properties / summary / properties / maintenance / description
      Previous value: -"Vendors with indicator = maintenance — in a scheduled window the vendor published. Counted apart from degraded and down, which are faults."New value: +"Vendors rated maintenance — in a scheduled window the vendor published, with no open incident rated minor or worse. Counted apart from degraded and down, which are faults."
    • changedOutput schema / properties / summary / properties / operational / description
      Previous value: -"Vendors with indicator = none and no error."New value: +"Vendors rated none — indicator none and no open incident rated minor or worse — and not errored."
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Components matching component_filter across all vendors before the cap. Present only when truncated."New value: +"Components matching component_filter across all vendors, before component_offset and the cap. Present only when truncated."
    • changedOutput schema / properties / truncated / description
      Previous value: -"True when at least one vendor's component list was capped at component_limit. Absent when nothing was capped."New value: +"True when at least one vendor has components past the returned page — those vendors carry next_component_offset. Absent otherwise, including on the last page of a list."
  2. Changed20 schema fields changed
    • changedInput schema / properties / component_filter / description
      Previous value: -"Case-insensitive substring matched against component names in detailed mode (e.g., \"api\" to check just the API components). Applied before component_limit, so it is the way to reach a component that the cap would otherwise omit. Ignored in summary mode."New value: +"Case-insensitive substring matched against component names and their group names in detailed mode (e.g., \"api\" to check just the API components, or a product or region a page groups components under). Applied before component_limit, so it is the way to reach a component that the cap would otherwise omit. A filter that matches nothing for a vendor is reported in notice. Ignored in summary mode."
    • changedInput schema / properties / component_limit / description
      Previous value: -"Maximum components returned per vendor in detailed mode (1-500). Large status pages publish hundreds of components, so a multi-vendor batch at a high limit returns a very large response; narrow with component_filter instead where possible."New value: +"Maximum components returned per vendor in detailed mode, at least 1. A value above 500 is reduced to 500, and notice says so. Large status pages publish hundreds of components, so a multi-vendor batch at a high limit returns a very large response; narrow with component_filter instead where possible."
    • changedInput schema / properties / component_limit / maximum
      Previous value: -500New value: +9007199254740991
    • changedInput schema / properties / vendors / description
      Previous value: -"Vendor slugs from the built-in registry (e.g., \"github\", \"aws\") or raw Atlassian Statuspage base URLs (non-Statuspage backends are supported via registry slugs only). Mix freely. Use devops_list_vendors to discover available slugs."New value: +"Vendor slugs from the built-in registry (e.g., \"github\", \"aws\") or raw Atlassian Statuspage base URLs (non-Statuspage backends are supported via registry slugs only). Mix freely. Use devops_list_vendors to discover available slugs. The first 20 are checked, in the order given; entries past the 20th are returned unchecked in deferred_vendors to resend in another call. Lists longer than 100 are rejected."
    • changedInput schema / properties / vendors / maxItems
      Previous value: -20New value: +100
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "not": {
      -      "required": [
      -        "error"
      -      ]
      -    },
      -    "required": [
      -      "results",
      -      "summary",
      -      "nextToolSuggestions"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "results",
      +      "deferred_vendors",
      +      "summary",
      +      "nextToolSuggestions"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / deferred_vendors
      Added value: +{
      +  "description": "Entries past the first 20 in vendors, verbatim and in input order. They were not checked; resend them in another call. Empty when every entry was checked.",
      +  "items": {
      +    "description": "A vendor entry exactly as provided.",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `vendor_not_found`: No requested vendor could be checked and the first failure was a slug that matches no registry entry and is not a valid URL. `target_blocked`: No requested vendor could be checked and the first failure was a raw URL resolving to a private, loopback, or cloud-metadata address. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `vendor_not_found`: No requested vendor among the first 20 could be checked and the first failure was a slug that matches no registry entry and is not a valid URL. `target_blocked`: No requested vendor among the first 20 could be checked and the first failure was a raw URL resolving to a private, loopback, or cloud-metadata address. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / nextToolSuggestions / items / properties / args / description
      Previous value: -"Ready-to-use devops_suggest_action arguments: vendor (registry slug, or the normalized status page URL for a raw URL), vendor_indicator (only for minor, major, or critical), affected_components (degraded components outside a maintenance window), incident_summary (title of the most recently started open incident rated minor or worse)."New value: +"Ready-to-use devops_suggest_action arguments: vendor (registry slug, or the normalized status page URL for a raw URL), vendor_indicator (only for minor, major, or critical), affected_components (degraded components outside a maintenance window, each written \"Group / Leaf\" when it is in a group), incident_summary (title of the most recently started open incident rated minor or worse)."
    • changedOutput schema / properties / notice / description
      Previous value: -"Plain-language explanation of the capped component lists — how many components were omitted and how to reach them (component_filter to target one, component_limit to raise the cap). Present only when truncated."New value: +"Plain-language explanation of what this call left out or adjusted: vendors past the first 20 (listed in deferred_vendors), a component_limit above 500 reduced to 500, and in detailed mode how many components the cap omitted and how to reach them (component_filter to target one, or component_limit to raise a cap below 500), and which checked vendors component_filter matched no component of, with how many each publishes. Present only when one of these applies."
    • changedOutput schema / properties / results / description
      Previous value: -"Per-vendor status results in the same order as the input vendors list."New value: +"Per-vendor status results for the vendors checked, in the same order as the input vendors list."
    • changedOutput schema / properties / results / items / properties / active_incidents / items / properties / latest_update / description
      Previous value: -"Most recent incident_update body text."New value: +"Most recent update text, as plain text: HTML markup the vendor published is converted, and any other < is text the vendor wrote."
    • changedOutput schema / properties / results / items / properties / all_components / description
      Previous value: -"Components including operational ones, capped at component_limit per vendor and narrowed by component_filter when given. Present in detailed mode only."New value: +"Components including operational ones, capped at component_limit per vendor and narrowed by component_filter (matched against name and group) when given. Present in detailed mode only."
    • addedOutput schema / properties / results / items / properties / all_components / items / properties / group
      Added value: +{
      +  "description": "Name of the group the status page files this component under — typically the product or region it belongs to — or null when it is not in a group.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / results / items / properties / all_components / items / properties / name / description
      Previous value: -"Component name."New value: +"Component name as the status page publishes it — the leaf alone, without its group. Several leaves can share a name (one per region or product); group tells them apart."
    • changedOutput schema / properties / results / items / properties / all_components / items / required
      Previous value: -[
      -  "name",
      -  "status",
      -  "description"
      -]New value: +[
      +  "name",
      +  "group",
      +  "status",
      +  "description"
      +]
    • addedOutput schema / properties / results / items / properties / degraded_components / items / properties / group
      Added value: +{
      +  "description": "Name of the group the status page files this component under — typically the product or region it belongs to — or null when it is not in a group.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / results / items / properties / degraded_components / items / properties / name / description
      Previous value: -"Component name."New value: +"Component name as the status page publishes it — the leaf alone, without its group. Several leaves can share a name (one per region or product); group tells them apart."
    • changedOutput schema / properties / results / items / properties / degraded_components / items / required
      Previous value: -[
      -  "name",
      -  "status"
      -]New value: +[
      +  "name",
      +  "group",
      +  "status"
      +]
    • changedOutput schema / properties / summary / properties / total / description
      Previous value: -"Total number of vendors checked."New value: +"Total number of vendors checked — never counts deferred_vendors."
  3. Changed3 schema fields changed
    • changedOutput schema / properties / results / items / properties / active_incidents / items / properties / started_at / description
      Previous value: -"ISO 8601 UTC timestamp when the incident started, or null/absent if not set by the vendor."New value: +"ISO 8601 timestamp, with the vendor's UTC offset (Z, +00:00, or a local offset such as -07:00), when the incident started, or null/absent if not set by the vendor."
    • changedOutput schema / properties / results / items / properties / scheduled_maintenances / items / properties / scheduled_for / description
      Previous value: -"ISO 8601 UTC start time."New value: +"ISO 8601 start time, with the vendor's UTC offset."
    • changedOutput schema / properties / results / items / properties / scheduled_maintenances / items / properties / scheduled_until / description
      Previous value: -"ISO 8601 UTC end time."New value: +"ISO 8601 end time, with the vendor's UTC offset."
  4. Changed2 schema fields changed
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "not": {
      -      "required": [
      -        "error"
      -      ]
      -    },
      -    "required": [
      -      "results",
      -      "summary"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "results",
      +      "summary",
      +      "nextToolSuggestions"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / nextToolSuggestions
      Added value: +{
      +  "description": "One devops_suggest_action call per vendor with an active problem — an indicator of minor, major, or critical, or an open incident of that impact even while the indicator reads none or maintenance — with its arguments filled from that vendor's result. Vendors that could not be checked never appear. Empty when no checked vendor has an active problem.",
      +  "items": {
      +    "additionalProperties": false,
      +    "description": "A recommended follow-up tool call with pre-filled arguments.",
      +    "properties": {
      +      "args": {
      +        "additionalProperties": {},
      +        "description": "Ready-to-use devops_suggest_action arguments: vendor (registry slug, or the normalized status page URL for a raw URL), vendor_indicator (only for minor, major, or critical), affected_components (degraded components outside a maintenance window), incident_summary (title of the most recently started open incident rated minor or worse).",
      +        "propertyNames": {
      +          "type": "string"
      +        },
      +        "type": "object"
      +      },
      +      "reason": {
      +        "description": "Why the vendor qualifies: its reported indicator, or the open incident behind it.",
      +        "type": "string"
      +      },
      +      "toolName": {
      +        "description": "Tool to call next — \"devops_suggest_action\".",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "toolName",
      +      "reason",
      +      "args"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  5. Changed4 schema fields changed
    • removedOutput schema / properties / results / items / properties / active_incidents / items / properties / started_at / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / active_incidents / items / properties / started_at / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / results / items / properties / all_components / items / properties / description / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / all_components / items / properties / description / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  6. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "results",
      +      "summary"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Present when the call failed. Absent on success.",
      +  "properties": {
      +    "code": {
      +      "description": "JSON-RPC error code for this failure.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "data": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "reason": {
      +          "description": "Machine-readable failure mode. Declared by this tool: `vendor_not_found`: No requested vendor could be checked and the first failure was a slug that matches no registry entry and is not a valid URL. `target_blocked`: No requested vendor could be checked and the first failure was a raw URL resolving to a private, loopback, or cloud-metadata address. Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "vendor_not_found",
      +            "target_blocked"
      +          ],
      +          "type": "string"
      +        },
      +        "recovery": {
      +          "additionalProperties": {},
      +          "description": "Actionable next step for the caller.",
      +          "properties": {
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "retryable": {
      +          "description": "Whether retrying may succeed.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable description of what went wrong.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "message"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "results",
      -  "summary"
      -]
  7. Changed6 schema fields changed
    • changedOutput schema / properties / results / items / properties / degraded_components / description
      Previous value: -"Components not in operational state. Empty when all clear."New value: +"Every component not in an operational state, uncapped — a vendor with a large edge-node fleet routinely publishes dozens. Includes in-progress maintenance windows (status under_maintenance) alongside genuine outages; read status to tell a planned window from a fault. Empty when all clear."
    • changedOutput schema / properties / results / items / properties / indicator / description
      Previous value: -"Overall health indicator: none = all clear, minor = some degradation, major = significant outage, critical = complete outage."New value: +"Overall health indicator: none = all clear, minor = some degradation, major = significant outage, critical = complete outage, maintenance = scheduled window in progress, planned rather than a fault."
    • changedOutput schema / properties / results / items / properties / indicator / enum
      Previous value: -[
      -  "none",
      -  "minor",
      -  "major",
      -  "critical"
      -]New value: +[
      +  "none",
      +  "minor",
      +  "major",
      +  "critical",
      +  "maintenance"
      +]
    • changedOutput schema / properties / summary / description
      Previous value: -"Aggregate health counts across all checked vendors. Buckets partition the batch: operational + degraded + down + unavailable = total."New value: +"Aggregate health counts across all checked vendors. Buckets partition the batch: operational + degraded + down + maintenance + unavailable = total."
    • addedOutput schema / properties / summary / properties / maintenance
      Added value: +{
      +  "description": "Vendors with indicator = maintenance — in a scheduled window the vendor published. Counted apart from degraded and down, which are faults.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / summary / required
      Previous value: -[
      -  "total",
      -  "operational",
      -  "degraded",
      -  "down",
      -  "unavailable"
      -]New value: +[
      +  "total",
      +  "operational",
      +  "degraded",
      +  "down",
      +  "maintenance",
      +  "unavailable"
      +]
  8. Changed1 schema field changed
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Plain-language explanation of the capped component lists — how many components were omitted and how to reach them (component_filter to target one, component_limit to raise the cap). Present only when truncated.",
      +  "type": "string"
      +}
  9. Changed13 schema fields changed
    • addedInput schema / properties / component_filter
      Added value: +{
      +  "description": "Case-insensitive substring matched against component names in detailed mode (e.g., \"api\" to check just the API components). Applied before component_limit, so it is the way to reach a component that the cap would otherwise omit. Ignored in summary mode.",
      +  "type": "string"
      +}
    • addedInput schema / properties / component_limit
      Added value: +{
      +  "default": 50,
      +  "description": "Maximum components returned per vendor in detailed mode (1-500). Large status pages publish hundreds of components, so a multi-vendor batch at a high limit returns a very large response; narrow with component_filter instead where possible.",
      +  "maximum": 500,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / mode / description
      Previous value: -"summary: indicator + degraded components + active incidents only. detailed: adds full component list and scheduled maintenance windows."New value: +"summary: indicator + degraded components + active incidents only. detailed: adds the component list and scheduled maintenance windows."
    • addedOutput schema / properties / cap
      Added value: +{
      +  "description": "The per-vendor component_limit that was applied. Present only when truncated.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / results / items / properties / all_components / description
      Previous value: -"All components including operational ones. Present in detailed mode only."New value: +"Components including operational ones, capped at component_limit per vendor and narrowed by component_filter when given. Present in detailed mode only."
    • addedOutput schema / properties / results / items / properties / all_components_total
      Added value: +{
      +  "description": "Components matching component_filter for this vendor before the component_limit cap. Larger than the length of all_components when this vendor was capped. Present in detailed mode only.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / shown
      Added value: +{
      +  "description": "Components returned across all vendors. Present only when truncated.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / summary / description
      Previous value: -"Aggregate health counts across all checked vendors."New value: +"Aggregate health counts across all checked vendors. Buckets partition the batch: operational + degraded + down + unavailable = total."
    • changedOutput schema / properties / summary / properties / operational / description
      Previous value: -"Vendors with indicator = none."New value: +"Vendors with indicator = none and no error."
    • addedOutput schema / properties / summary / properties / unavailable
      Added value: +{
      +  "description": "Vendors that could not be checked (carry an error) — unresolvable slug, blocked target, or failed status fetch. Counted as unknown, never operational.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / summary / required
      Previous value: -[
      -  "total",
      -  "operational",
      -  "degraded",
      -  "down"
      -]New value: +[
      +  "total",
      +  "operational",
      +  "degraded",
      +  "down",
      +  "unavailable"
      +]
    • addedOutput schema / properties / totalCount
      Added value: +{
      +  "description": "Components matching component_filter across all vendors before the cap. Present only when truncated.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / truncated
      Added value: +{
      +  "description": "True when at least one vendor's component list was capped at component_limit. Absent when nothing was capped.",
      +  "type": "boolean"
      +}
  10. Changed3 schema fields changed
    • changedOutput schema / properties / results / items / properties / active_incidents / items / properties / impact / description
      Previous value: -"Severity level: none = informational, minor = degraded performance, major = partial outage, critical = full outage."New value: +"Severity level: none = informational, minor = degraded performance, major = partial outage, critical = full outage, maintenance = scheduled window folded into incident history."
    • changedOutput schema / properties / results / items / properties / active_incidents / items / properties / impact / enum
      Previous value: -[
      -  "none",
      -  "minor",
      -  "major",
      -  "critical"
      -]New value: +[
      +  "none",
      +  "minor",
      +  "major",
      +  "critical",
      +  "maintenance"
      +]
    • changedOutput schema / properties / results / items / properties / error / description
      Previous value: -"Fetch error message. Absent when the vendor was fetched successfully."New value: +"Why this vendor could not be checked — unreachable status API, timeout, non-2xx, or a response that is not a Statuspage payload. Reported here rather than thrown so one bad vendor does not fail the batch. Absent when the vendor was fetched successfully."
  11. Changed4 schema fields changed
    • changedInput schema / properties / vendors / description
      Previous value: -"Vendor slugs from the built-in registry (e.g., \"github\", \"cloudflare\") or raw Statuspage base URLs. Mix freely. Use devops_list_vendors to discover available slugs."New value: +"Vendor slugs from the built-in registry (e.g., \"github\", \"aws\") or raw Atlassian Statuspage base URLs (non-Statuspage backends are supported via registry slugs only). Mix freely. Use devops_list_vendors to discover available slugs."
    • changedInput schema / properties / vendors / items / description
      Previous value: -"A vendor slug (e.g., \"github\") or raw Statuspage base URL."New value: +"A vendor slug (e.g., \"github\") or raw Atlassian Statuspage base URL."
    • changedOutput schema / properties / results / items / properties / active_incidents / items / properties / id / description
      Previous value: -"Unique incident identifier from Statuspage."New value: +"Unique incident identifier from the vendor's status API."
    • changedOutput schema / properties / results / items / properties / statuspage_url / description
      Previous value: -"Statuspage base URL used for this vendor."New value: +"Status page base URL used for this vendor."
  12. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover safety (readOnly/idempotent/openWorld), and the description adds substantial operational context beyond them: a 20-vendor per-call cap with deferred_vendors, per-vendor error isolation ("one bad entry never discards the rest"), cross-backend normalization, summary semantics (worse of indicator and worst incident), and the nextToolSuggestions side effect.

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?

Purpose and batching guidance are front-loaded, and most sentences carry real information. The long inline vendor-backend parenthesis and some redundant restatement of schema-documented parameters add bulk without much payoff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a batch fan-out tool over external status APIs, the description covers the failure mode, the size cap, the refresh/resend workflow, and the interpretation of indicator values. An output schema exists, but the description still clarifies what the indicator levels mean, which is genuinely useful.

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 100% and the schema already explains mode, component_filter, component_limit, and component_offset in greater depth than the description does. The description only restates them in compressed form ("narrowed with component_filter, bounded by component_limit, and paged with component_offset"), so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Check the current health status for one or more vendors") and immediately pins the scope: registered vendor slugs or raw Statuspage URLs. It is clearly distinct from siblings like devops_check_certs, devops_check_dns, and devops_get_incidents.

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?

Gives concrete routing within the tool ("Use mode: 'detailed' for component lists and maintenance windows") and a batching strategy ("pass a list to check your full stack in one call"). It does not explicitly contrast with devops_get_incidents, which also surfaces incidents, so an agent still has to infer that boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.