GraphOS MCP Server

GetOperationMetrics

Read-onlyIdempotent

Top operations by usage/health for a graph over a time window, as compact CSV. Columns: start timestamp, end exclusive timestamp, operation name, request count, request latency p50 ms, request latency p99 ms, request with error count. Ranked by orderBy descending: default REQUEST_COUNT (busiest); REQUEST_WITH_ERROR_COUNT for most error-prone, REQUEST_LATENCY_P99_MS for slowest. variantName scopes to one or more variants (omit for all). clients scopes to one or more clients; omit clientVersion to match every version of that client, and use GetClientMetrics to discover the names a graph sees. Keep the default resolution of ENTIRE_RANGE for totals and top-N, which gives one row per operation ranked over the whole window. DAY/HOUR/MINUTE give one row per operation per bucket ranked within each bucket, so a window total then needs a per-operation sum plus a limit big enough to cover every bucket; too small a limit silently undercounts. Only HOUR and MINUTE accept a to of now, so use them for bursts in the last 24 hours. Avoid MONTH: it labels buckets by calendar month, not by the requested window.

Input Schema

Name	Required	Description	Default
`to`	Yes	The ending timestamp for the report. Must be in the format: 2025-01-01T08:00:00Z (ISO 8601). This timestamp cannot exceed your plan's operation-level data retention as defined in the Apollo GraphQL pricing page (https://www.apollographql.com/pricing).
`from`	Yes	The starting timestamp for the report. Must be in the format: 2025-01-01T00:00:00Z (ISO 8601). This timestamp cannot exceed your plan's operation-level data retention as defined in the Apollo GraphQL pricing page (https://www.apollographql.com/pricing).
`limit`	No	Maximum number of records to return (default: 100, max 10000).
`clients`	No
`graphId`	Yes
`orderBy`	No		REQUEST_COUNT
`resolution`	No	The resolution of the time groups for the report. This resolution will affect the range of times that can be used for the 'from' and 'to' timestamps: - For the MINUTE resolution, the total time between 'from' and 'to' must be no more than 1 day, and the 'from' time must be no earlier than 30 days ago. - For the HOUR resolution, the total time between 'from' and 'to' must be no more than 7 days, and the 'from' time must be no earlier than 90 days ago. - For the DAY, MONTH, and ENTIRE_RANGE resolutions, the 'from' time must be no earlier than 549 days ago (approx 18 months), and the 'to' time must be no later than 1 day ago. - These time ranges are further constrained by your plan's operation-level data retention as defined in the Apollo GraphQL pricing page (https://www.apollographql.com/pricing). If these criteria are not met, this will return a REQUEST_INVALID error.	ENTIRE_RANGE
`variantName`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

changedInput schema / properties / from / description

Previous value: -"The starting timestamp for the report. Must be in the format: 2025-01-01T00:00:00Z (ISO 8601)."New value: +"The starting timestamp for the report. Must be in the format: 2025-01-01T00:00:00Z (ISO 8601). This timestamp cannot exceed your plan's operation-level data retention as defined in the Apollo GraphQL pricing page (https://www.apollographql.com/pricing)."

changedInput schema / properties / resolution / description

Previous value: -"The resolution of the time groups for the report. This resolution will affect the range of times that can be used for the 'from' and\n'to' timestamps:\n- For the MINUTE resolution, the total time between 'from' and 'to' must be no more than 1 day, and the 'from' time must be no earlier than 30 days ago.\n- For the HOUR resolution, the total time between 'from' and 'to' must be no more than 7 days, and the 'from' time must be no earlier than 90 days ago.\n- For the DAY, MONTH, and ENTIRE_RANGE resolutions, the 'from' time must be no earlier than 549 days ago (approx 18 months), and the 'to' time must be no later than 1 day ago.\nIf these criteria are not met, this will return a REQUEST_INVALID error."New value: +"The resolution of the time groups for the report. This resolution will affect the range of times that can be used for the 'from' and\n'to' timestamps:\n- For the MINUTE resolution, the total time between 'from' and 'to' must be no more than 1 day, and the 'from' time must be no earlier than 30 days ago.\n- For the HOUR resolution, the total time between 'from' and 'to' must be no more than 7 days, and the 'from' time must be no earlier than 90 days ago.\n- For the DAY, MONTH, and ENTIRE_RANGE resolutions, the 'from' time must be no earlier than 549 days ago (approx 18 months), and the 'to' time must be no later than 1 day ago.\n- These time ranges are further constrained by your plan's operation-level data retention as defined in the Apollo GraphQL pricing page (https://www.apollographql.com/pricing).\nIf these criteria are not met, this will return a REQUEST_INVALID error."

changedInput schema / properties / to / description

Previous value: -"The ending timestamp for the report. Must be in the format: 2025-01-01T08:00:00Z (ISO 8601)."New value: +"The ending timestamp for the report. Must be in the format: 2025-01-01T08:00:00Z (ISO 8601). This timestamp cannot exceed your plan's operation-level data retention as defined in the Apollo GraphQL pricing page (https://www.apollographql.com/pricing)."

Changed21 schema fields changedSep 18, 2026

addedInput schema / definitions / OperationInsightsTimeseriesReportClientFilterInInput / properties / clientName / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
removedInput schema / definitions / OperationInsightsTimeseriesReportClientFilterInInput / properties / clientName / type
```
Removed value: -"string"
```
addedInput schema / definitions / OperationInsightsTimeseriesReportClientFilterInInput / properties / clientVersion / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
removedInput schema / definitions / OperationInsightsTimeseriesReportClientFilterInInput / properties / clientVersion / type
```
Removed value: -"string"
```

addedInput schema / properties / clients / anyOf

Added value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "$ref": "#/definitions/OperationInsightsTimeseriesReportClientFilterInInput"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / clients / items

Removed value: -{
-  "oneOf": [
-    {
-      "$ref": "#/definitions/OperationInsightsTimeseriesReportClientFilterInInput"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedInput schema / properties / clients / type
```
Removed value: -"array"
```

addedInput schema / properties / limit / anyOf

Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / limit / default
```
Added value: +50
```
removedInput schema / properties / limit / type
```
Removed value: -"integer"
```

removedInput schema / properties / orderBy / $ref

Removed value: -"#/definitions/OperationInsightsTimeseriesReportMetric"

addedInput schema / properties / orderBy / anyOf

Added value: +[
+  {
+    "$ref": "#/definitions/OperationInsightsTimeseriesReportMetric"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / orderBy / default
```
Added value: +"REQUEST_COUNT"
```

removedInput schema / properties / resolution / $ref

Removed value: -"#/definitions/TimeseriesReportResolution"

addedInput schema / properties / resolution / anyOf

Added value: +[
+  {
+    "$ref": "#/definitions/TimeseriesReportResolution"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / resolution / default
```
Added value: +"ENTIRE_RANGE"
```

addedInput schema / properties / variantName / anyOf

Added value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / variantName / items

Removed value: -{
-  "oneOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedInput schema / properties / variantName / type
```
Removed value: -"array"
```

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

Added value: +[
+  {
+    "properties": {
+      "operationInsightsTimeseriesReport": {
+        "description": " Returns a timeseries of operation metrics across a specified time range for this graph. This will return specified metrics (request count,\n avg latency, etc) grouped by time and the specified dimensions (query ID, query name, client name, etc). This API is rate limited and only\n allows a small number of requests per minute, and will return a RATE_LIMIT_EXCEEDED error if too many requests are made for a graph. If a\nrequest to this field times out, we recommend that you try a shorter time range or fewer dimensions.",
+        "properties": {
+          "csv": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "A CSV representation of the results. This includes a header and rows that have a column for start and end timestamp and all requested dimensions and metrics."
+          }
+        },
+        "type": "object"
+      }
+    },
+    "required": [
+      "operationInsightsTimeseriesReport"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

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

Removed value: -[
-  {
-    "properties": {
-      "operationInsightsTimeseriesReport": {
-        "description": " Returns a timeseries of operation metrics across a specified time range for this graph. This will return specified metrics (request count,\n avg latency, etc) grouped by time and the specified dimensions (query ID, query name, client name, etc). This API is rate limited and only\n allows a small number of requests per minute, and will return a RATE_LIMIT_EXCEEDED error if too many requests are made for a graph. If a\nrequest to this field times out, we recommend that you try a shorter time range or fewer dimensions.",
-        "properties": {
-          "csv": {
-            "description": "A CSV representation of the results. This includes a header and rows that have a column for start and end timestamp and all requested dimensions and metrics.",
-            "oneOf": [
-              {
-                "type": "string"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          }
-        },
-        "type": "object"
-      }
-    },
-    "required": [
-      "operationInsightsTimeseriesReport"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]

Changed4 schema fields changedSep 11, 2026

addedInput schema / definitions / OperationInsightsTimeseriesReportClientFilterInInput

Added value: +{
+  "description": "The named type and version of the clients to include or exclude in the operation timeseries report.",
+  "properties": {
+    "clientName": {
+      "description": "The client name.",
+      "type": "string"
+    },
+    "clientVersion": {
+      "description": "The client version.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / definitions / TimeseriesReportResolution

Added value: +{
+  "description": "The size of each time bucket in a timeseries report.\n\nValues:\nDAY: One-day buckets.\nENTIRE_RANGE: Single bucket containing the entire time range.\nHOUR: One-hour buckets.\nMINUTE: One-minute buckets.\nMONTH: One-month buckets.",
+  "enum": [
+    "DAY",
+    "ENTIRE_RANGE",
+    "HOUR",
+    "MINUTE",
+    "MONTH"
+  ],
+  "type": "string"
+}

addedInput schema / properties / clients

Added value: +{
+  "items": {
+    "oneOf": [
+      {
+        "$ref": "#/definitions/OperationInsightsTimeseriesReportClientFilterInInput"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "type": "array"
+}

addedInput schema / properties / resolution

Added value: +{
+  "$ref": "#/definitions/TimeseriesReportResolution",
+  "description": "The resolution of the time groups for the report. This resolution will affect the range of times that can be used for the 'from' and\n'to' timestamps:\n- For the MINUTE resolution, the total time between 'from' and 'to' must be no more than 1 day, and the 'from' time must be no earlier than 30 days ago.\n- For the HOUR resolution, the total time between 'from' and 'to' must be no more than 7 days, and the 'from' time must be no earlier than 90 days ago.\n- For the DAY, MONTH, and ENTIRE_RANGE resolutions, the 'from' time must be no earlier than 549 days ago (approx 18 months), and the 'to' time must be no later than 1 day ago.\nIf these criteria are not met, this will return a REQUEST_INVALID error."
+}

First observedAug 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover the read-only, idempotent safety profile, and the description adds behavior the agent could not otherwise know: buckets are ranked within themselves so a window total requires per-operation summation, a too-small `limit` silently undercounts, and the end timestamp is exclusive. Those silent-failure caveats are exactly the kind of disclosure that prevents wrong answers.

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 column layout first, then ranking, then scoping, then resolution trade-offs — a sensible information order. It is dense prose in one block and a few clauses (e.g. restating the resolution/`to`-of-now interaction) could be tightened, but nearly every sentence carries actionable content for an 8-parameter tool.

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 values need not be explained, yet the description still gives the CSV column order, which makes parsing unambiguous. Combined with the annotations and the resolution/limit pitfalls, an agent has everything needed to call this correctly on the first try.

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

Parameters5/5

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

Schema coverage is only 50%, but the description compensates heavily: it defines what `orderBy` values mean and that ranking is descending, explains multi-value scoping for `variantName` and `clients`, states the `clientVersion` omission trick, and characterizes `resolution` choices by row-granularity rather than just restating the enum. It goes well beyond the schema's bare field descriptions.

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?

The first sentence names a specific resource (top operations for a graph over a time window) plus the output format (compact CSV), and the column list makes the result shape unmistakable. It explicitly names GetClientMetrics as the companion for client-name discovery, but does not distinguish itself from the similar-sounding siblings GetTopOperations or GetSubgraphMetrics, so an agent must still infer which of those to pick.

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?

Guidance is explicit and conditional: keep ENTIRE_RANGE for totals/top-N, switch to DAY/HOUR/MINUTE for per-bucket comparisons, use HOUR/MINUTE for bursts in the last 24 hours since only they accept `to` of now, and avoid MONTH entirely. It also states the omission semantics for `clientVersion` (all versions) and routes to GetClientMetrics for discovering names.

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?