Opsphere — DevOps & SRE Intelligence

Synthetics summary by location

synthetics_summary_by_location

Read-only

Bounded Datadog Synthetics execution summary grouped by location (pass/fail of latest run — NOT config status). Filter by nameContains or publicIds for the requested environment/site/service. At most five tests are queried to protect the shared workspace queue; partial=true means the result is not complete. Prefer dd_synthetics_results for one exact test. Never claim 100% up when dataQuality reports missing or partial results.

Input Schema

Name	Required	Description
`hours`	No	Lookback window in hours for latest execution results (default 1, max 24)
`maxTests`	No	Maximum matching tests to query; bounded to five
`publicIds`	No	Exact Synthetic public IDs from tenant catalog evidence
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`nameContains`	No	Case-insensitive test-name filter for the requested environment/site/service

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / data / properties / byLocation / $ref
```
Removed value: -"#/properties/data/properties/items"
```

addedOutput schema / properties / data / properties / byLocation / items

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "failed": {
+      "type": "number"
+    },
+    "location": {
+      "type": "string"
+    },
+    "passed": {
+      "type": "number"
+    },
+    "tests": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / data / properties / byLocation / type
```
Added value: +"array"
```

addedOutput schema / properties / data / properties / executionCounts

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "failed": {
+      "type": "number"
+    },
+    "no_data": {
+      "type": "number"
+    },
+    "passed": {
+      "type": "number"
+    },
+    "unknown": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "passed",
+    "failed",
+    "no_data",
+    "unknown"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / data / properties / filters

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "maxTests": {
+      "type": "number"
+    },
+    "nameContains": {
+      "type": "string"
+    },
+    "publicIds": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / data / properties / items / items / $ref
```
Removed value: -"#/properties/data/properties/window"
```
addedOutput schema / properties / data / properties / items / items / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / data / properties / items / items / properties

Added value: +{
+  "config_status": {
+    "type": "string"
+  },
+  "latest_check_time": {
+    "type": "number"
+  },
+  "latest_execution_status": {
+    "type": "string"
+  },
+  "latest_probe_dc": {
+    "type": "string"
+  },
+  "latest_result_id": {
+    "type": "string"
+  },
+  "locations": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "name": {
+    "type": "string"
+  },
+  "public_id": {
+    "type": "string"
+  },
+  "status": {
+    "type": "string"
+  },
+  "type": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / data / properties / items / items / type
```
Added value: +"object"
```
addedOutput schema / properties / data / properties / matchedCount
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / data / properties / omittedCount
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / data / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / data / properties / totalAvailable
```
Added value: +{
+  "type": "number"
+}
```
removedOutput schema / properties / data / properties / warnings / items / $ref
```
Removed value: -"#/properties/data/properties/window"
```
addedOutput schema / properties / data / properties / warnings / items / additionalProperties
```
Added value: +false
```
addedOutput schema / properties / data / properties / warnings / items / properties
```
Added value: +{
+  "error": {
+    "type": "string"
+  }
+}
```
addedOutput schema / properties / data / properties / warnings / items / required
```
Added value: +[
+  "error"
+]
```
addedOutput schema / properties / data / properties / warnings / items / type
```
Added value: +"object"
```
changedOutput schema / properties / data / properties / window / additionalProperties
```
Previous value: -trueNew value: +false
```
addedOutput schema / properties / data / properties / window / properties / fromTs
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / data / properties / window / properties / toTs
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / data / properties / window / required
```
Added value: +[
+  "fromTs",
+  "toTs"
+]
```

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 2,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing the query bound ('At most five tests are queried to protect the shared workspace queue') and the meaning of the partial=true indicator. That operational-limit and result-fidelity context is exactly what an agent needs to avoid over-claiming.

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?

Front-loads purpose, then filtering, then the cost bound, then the alternative — a sensible ordering with little waste. The final caution sentence is guidance rather than definition, but it earns its place by shaping how results are reported.

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?

An output schema exists, so return shape needn't be explained, and the description still clarifies the two things the schema can't: the five-test cap and how to interpret partial/dataQuality. Nothing needed to call or report on this tool is missing.

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 hours, maxTests, publicIds, nameContains and context_id are already fully documented; the description only echoes the nameContains/publicIds filtering intent. Per the coverage baseline, no param text is needed, so a 3 is the ceiling here.

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 ('Datadog Synthetics execution summary grouped by location') plus a crucial scope qualifier ('pass/fail of latest run — NOT config status') that rules out the most likely misreading. An agent can distinguish it from dd_synthetics_results and dd_synthetics_summary without opening any schema.

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

Usage Guidelines5/5

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

Names the alternative explicitly ('Prefer dd_synthetics_results for one exact test') with the condition that selects it, and adds a hard reporting rule ('Never claim 100% up when dataQuality reports missing or partial results'). Both when-to-use and when-not-to-assert are spelled out.

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

All Opsphere — DevOps & SRE Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?