Tideways MCP Server

Get performance summary

tideways_get_performance_summary

Read-onlyIdempotent

Retrieve requests, errors, and p95 response time in 15-minute buckets for trend analysis, before/after comparisons, and incident detection.

Instructions

Requests, errors and p95 response time in 15-minute buckets for the last hours hours (up to ~30 days), with totals. Use for trends, before/after comparisons and spotting incidents. For per-minute detail and top transactions use tideways_get_performance.

Input Schema

Name	Required	Description	Default
`hours`	No	How many hours back to include (max 744 = 31 days). The API always returns ~30 days.
`detail`	No	"concise" (default) returns a trimmed summary. "full" also includes the unmodified API response under "raw"; it can be very large.	concise
`project`	No	Tideways project as "project" or "organization/project". Defaults to the defaultProject that tideways_list_projects reports; call it for valid names.
`service`	No	Service, e.g. "web" or "worker". Defaults to the configured service, else the project's default service. A project can have several services; tideways_list_services lists them. When results come back, an unknown name fails with an error.
`environment`	No	Environment, e.g. "production" or "staging". Defaults to the configured environment, else production; criteria.environment (traces: each trace's environment) shows which was used. When results come back, an unknown name fails with an error.

Output Schema

Name	Required	Description
`raw`	No	Unmodified Tideways API response; present only when detail is "full".
`totals`	Yes
`window`	Yes
`buckets`	Yes	15-minute buckets, oldest first; a bucket keyed 12:00 covers 12:00-12:14 UTC
`project`	Yes
`criteria`	Yes	What Tideways actually queried. Times are UTC "YYYY-MM-DD HH:mm".
`pendingBuckets`	Yes	Most recent buckets Tideways has not aggregated yet (zero-filled by the API), left out

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv2.1.1Oct 15, 2026

addedOutput schema / properties / buckets / items / properties / time / description
```
Added value: +"\"YYYY-MM-DD HH:mm\""
```
addedOutput schema / properties / buckets / items / properties / time / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2} \\d{2}:\\d{2}$"
```

addedOutput schema / properties / criteria / properties / end / anyOf

Added value: +[
+  {
+    "description": "\"YYYY-MM-DD HH:mm\"",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2} \\d{2}:\\d{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / criteria / properties / end / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedOutput schema / properties / criteria / properties / start / anyOf

Added value: +[
+  {
+    "description": "\"YYYY-MM-DD HH:mm\"",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2} \\d{2}:\\d{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / criteria / properties / start / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedOutput schema / properties / window / properties / from / anyOf

Added value: +[
+  {
+    "description": "\"YYYY-MM-DD HH:mm\"",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2} \\d{2}:\\d{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / window / properties / from / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedOutput schema / properties / window / properties / to / anyOf

Added value: +[
+  {
+    "description": "\"YYYY-MM-DD HH:mm\"",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2} \\d{2}:\\d{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / window / properties / to / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

First observedv2.0.0Oct 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 readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds useful behavioral context beyond that: the aggregation granularity (15-minute buckets), the retention window (~30 days), and that totals are included. It stops short of disclosing latency, rate limits or auth requirements, so it edges above baseline without being exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, zero waste, and front-loaded with the return shape before the routing advice. Each sentence earns its place.

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?

With an output schema handling return values, full parameter documentation, and annotations covering the safety profile, the description only needs to add granularity and routing – both of which it does. An agent has everything required to call it correctly.

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 every parameter is already documented (hours limits, detail concise/full, project/service/environment resolution and fallbacks). The description only echoes the `hours` window, adding no syntax or format meaning beyond the schema, so the baseline of 3 is correct.

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 plus exactly what is returned: requests, errors and p95 response time in 15-minute buckets with totals. It explicitly names the sibling tool that handles a different granularity (tideways_get_performance), so the agent can tell the two apart without opening either 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?

"Use for trends, before/after comparisons and spotting incidents" gives concrete use cases, and "For per-minute detail and top transactions use tideways_get_performance" names the alternative and the condition that selects it. Nothing is left to inference.

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

Deploy Server