GraphOS MCP Server

GetLaunchHistory

Read-onlyIdempotent

Retrieve recent launches for a graph variant (most recent first) to detect deployment instability such as repeated failures or frequent superseded launches. Each entry includes the launch id, status, and timestamps, so you can identify a specific launch and drill into it with GetLaunch. Use to assess deployment stability. Provide the graph ID, variant name, and optionally a limit (default 20 most recent launches, max 100 per page) and an offset to page further back.

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`graphId`	Yes
`variant`	Yes

Output Schema

Name	Required	Description	Default
`data`	No
`errors`	No
`extensions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 18, 2026

addedInput schema / properties / limit / default
```
Added value: +20
```
addedInput schema / properties / offset / default
```
Added value: +0
```

changedInput schema / required

Previous value: -[
-  "graphId",
-  "variant",
-  "limit",
-  "offset"
-]New value: +[
+  "graphId",
+  "variant"
+]

addedOutput schema / properties / data / properties / graph / anyOf

Added value: +[
+  {
+    "properties": {
+      "variant": {
+        "anyOf": [
+          {
+            "properties": {
+              "launchSummaries": {
+                "anyOf": [
+                  {
+                    "items": {
+                      "properties": {
+                        "completedAt": {
+                          "anyOf": [
+                            {
+                              "description": "ISO 8601, extended format with nanoseconds, Zulu (or \"[+-]seconds\" as a string or number relative to now)"
+                            },
+                            {
+                              "type": "null"
+                            }
+                          ],
+                          "description": "The timestamp when the launch completed. This value is null until the launch completes."
+                        },
+                        "createdAt": {
+                          "description": "ISO 8601, extended format with nanoseconds, Zulu (or \"[+-]seconds\" as a string or number relative to now)"
+                        },
+                        "id": {
+                          "description": "The unique identifier for this launch.",
+                          "oneOf": [
+                            {
+                              "type": "string"
+                            },
+                            {
+                              "type": "integer"
+                            }
+                          ]
+                        },
+                        "status": {
+                          "$ref": "#/definitions/LaunchStatus",
+                          "description": "The launch's status. If a launch is superseded, its status remains `LAUNCH_INITIATED`. To check for a superseded launch, use `supersededAt`."
+                        }
+                      },
+                      "required": [
+                        "id",
+                        "status",
+                        "createdAt"
+                      ],
+                      "type": "object"
+                    },
+                    "type": "array"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "A list of launches metadata ordered by date, asc or desc depending on orderBy. The maximum limit is 100."
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Provides details of the graph variant with the provided `name`, if a variant\nwith that name exists for this graph. Otherwise, returns null.\n\n For a list of _all_ variants associated with a graph, use `Graph.variants` instead."
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / data / properties / graph / oneOf

Removed value: -[
-  {
-    "properties": {
-      "variant": {
-        "description": "Provides details of the graph variant with the provided `name`, if a variant\nwith that name exists for this graph. Otherwise, returns null.\n\n For a list of _all_ variants associated with a graph, use `Graph.variants` instead.",
-        "oneOf": [
-          {
-            "properties": {
-              "launchSummaries": {
-                "description": "A list of launches metadata ordered by date, asc or desc depending on orderBy. The maximum limit is 100.",
-                "oneOf": [
-                  {
-                    "items": {
-                      "properties": {
-                        "completedAt": {
-                          "description": "The timestamp when the launch completed. This value is null until the launch completes.",
-                          "oneOf": [
-                            {
-                              "description": "ISO 8601, extended format with nanoseconds, Zulu (or \"[+-]seconds\" as a string or number relative to now)"
-                            },
-                            {
-                              "type": "null"
-                            }
-                          ]
-                        },
-                        "createdAt": {
-                          "description": "ISO 8601, extended format with nanoseconds, Zulu (or \"[+-]seconds\" as a string or number relative to now)"
-                        },
-                        "id": {
-                          "description": "The unique identifier for this launch.",
-                          "oneOf": [
-                            {
-                              "type": "string"
-                            },
-                            {
-                              "type": "integer"
-                            }
-                          ]
-                        },
-                        "status": {
-                          "$ref": "#/definitions/LaunchStatus",
-                          "description": "The launch's status. If a launch is superseded, its status remains `LAUNCH_INITIATED`. To check for a superseded launch, use `supersededAt`."
-                        }
-                      },
-                      "required": [
-                        "id",
-                        "status",
-                        "createdAt"
-                      ],
-                      "type": "object"
-                    },
-                    "type": "array"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]

Changed2 schema fields changedAug 4, 2026

addedInput schema / properties / offset
```
Added value: +{
+  "type": "integer"
+}
```

changedInput schema / required

Previous value: -[
-  "graphId",
-  "variant",
-  "limit"
-]New value: +[
+  "graphId",
+  "variant",
+  "limit",
+  "offset"
+]

First observedAug 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds useful non-annotation behavior: result ordering (most recent first), default page size of 20, and a 100-per-page cap, plus the fact that entries include id, status, and timestamps. It stops short of describing status value semantics or failure modes, so not a full 5.

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-loaded with purpose and ordering in the first sentence, then return contents, use case, and parameters. The standalone sentence 'Use to assess deployment stability' is somewhat redundant with the opening sentence's mention of detecting instability, costing a little efficiency.

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 and annotations cover safety semantics, so the description need not explain return values—and it references them only enough to enable drill-down. Paging, ordering, defaults, and caps are all covered; the remaining gap is not defining what status/timestamp fields mean or how variant naming works.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description has to carry parameter meaning—and it does for limit (default 20, max 100) and offset (paging further back), which the schema does not express. graphId and variant are only named, not explained, leaving a small gap for the two required parameters.

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 ('Retrieve recent launches for a graph variant'), plus ordering ('most recent first') and a concrete analytical purpose (detecting instability). It also distinguishes itself from the sibling GetLaunch by describing that tool as the drill-down step.

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?

Explicitly names the scenario ('assess deployment instability such as repeated failures or frequent superseded launches') and points to the alternative GetLaunch for drilling into a specific launch id. An agent can decide between this and GetLaunch/GetLatestLaunch without further inference.

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

All GraphOS MCP Server 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?