Synapse Layer — Trust Infrastructure for AI Agents

slo_report

Read-only

Return uptime and SLO metrics for the MCP service.

Input Schema

Name	Required	Description	Default
`admin_token`	Yes	Admin authentication token. Must match ADMIN_TOKEN environment variable.
`window_hours`	No	Time windows in hours for the report. Default: [24, 168] (24h + 7d).

Output Schema

Name	Required	Description	Default
`status`	Yes
`version`	No
`windows`	No
`generatedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 29, 2026

removedOutput schema / properties / errorRate
```
Removed value: -{
-  "type": "number"
-}
```
addedOutput schema / properties / generatedAt
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / p50

Removed value: -{
-  "type": "number"
-}

removedOutput schema / properties / p95

Removed value: -{
-  "type": "number"
-}

addedOutput schema / properties / status
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / uptime

Removed value: -{
-  "type": "number"
-}

addedOutput schema / properties / version
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / window

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / windows

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "uptime"
-]New value: +[
+  "generatedAt",
+  "status"
+]

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "errorRate": {
+      "type": "number"
+    },
+    "p50": {
+      "type": "number"
+    },
+    "p95": {
+      "type": "number"
+    },
+    "uptime": {
+      "type": "number"
+    },
+    "window": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "uptime"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 6, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "code": {
-      "description": "Error code on admin-auth failure.",
-      "type": "string"
-    },
-    "error": {
-      "description": "Present only on admin-auth failure.",
-      "type": "string"
-    },
-    "generatedAt": {
-      "type": "string"
-    },
-    "status": {
-      "enum": [
-        "nominal",
-        "degraded",
-        "insufficient_data"
-      ],
-      "type": "string"
-    },
-    "version": {
-      "type": "string"
-    },
-    "windows": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "avgLatencyMs": {
-            "type": "number"
-          },
-          "errorRate": {
-            "type": "number"
-          },
-          "p50LatencyMs": {
-            "type": "number"
-          },
-          "p95LatencyMs": {
-            "type": "number"
-          },
-          "p99LatencyMs": {
-            "type": "number"
-          },
-          "toolBreakdown": {
-            "additionalProperties": true,
-            "type": "object"
-          },
-          "topErrors": {
-            "items": {
-              "additionalProperties": true,
-              "properties": {
-                "count": {
-                  "type": "number"
-                },
-                "errorCode": {
-                  "type": "string"
-                }
-              },
-              "type": "object"
-            },
-            "type": "array"
-          },
-          "totalRequests": {
-            "type": "number"
-          },
-          "windowHours": {
-            "type": "number"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedAug 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "code": {
+      "description": "Error code on admin-auth failure.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Present only on admin-auth failure.",
+      "type": "string"
+    },
+    "generatedAt": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "nominal",
+        "degraded",
+        "insufficient_data"
+      ],
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    },
+    "windows": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "avgLatencyMs": {
+            "type": "number"
+          },
+          "errorRate": {
+            "type": "number"
+          },
+          "p50LatencyMs": {
+            "type": "number"
+          },
+          "p95LatencyMs": {
+            "type": "number"
+          },
+          "p99LatencyMs": {
+            "type": "number"
+          },
+          "toolBreakdown": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "topErrors": {
+            "items": {
+              "additionalProperties": true,
+              "properties": {
+                "count": {
+                  "type": "number"
+                },
+                "errorCode": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "totalRequests": {
+            "type": "number"
+          },
+          "windowHours": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedMay 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only the subject matter (MCP service uptime/SLO); it does not mention the admin-token gate, failure behavior on bad auth, or cost/latency of querying multiple windows, so it adds little beyond structured data.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently sized, though it borders on terse for a tool with an auth prerequisite and a configurable multi-window parameter.

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?

An output schema exists, so return values need no explanation, and both parameters are fully described in the schema. What remains unaddressed is minor operational context — auth failure modes and whether windows are computed independently — but nothing blocks correct invocation.

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%, so admin_token's auth requirement and window_hours' default ([24, 168]) are already fully documented in the schema. The description adds no interpretation of the window array (e.g., allowed ranges, granularity returned), so baseline 3 applies.

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?

States a specific verb ("Return") and a specific resource ("uptime and SLO metrics") scoped to the MCP service. An agent can tell exactly what this produces; no sibling differentiation is needed because all listed siblings are memory/text tools with no overlap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied — an agent infers this is for health/SLO monitoring. There is no explicit when-to-use, when-not-to-use, or pointer to a related tool (e.g., health_check for a lightweight liveness probe vs. this for full metric windows).

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

All Synapse Layer — Trust Infrastructure for AI Agents tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

slo_report

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources