Tideways MCP Server

Get performance summary

tideways_get_performance_summary

Read-onlyIdempotent

Retrieve requests, errors, and p95 response time in 15-minute buckets over a chosen time range to spot trends, compare periods, and detect incidents.

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

TableJSON 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

TableJSON 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.

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 readOnly, idempotent, non-destructive and openWorld. The description adds real behavioral detail beyond them: 15-minute bucket granularity, an effective ~30-day window, and that totals are included. It does not discuss rate limits, auth, or result ordering, so it is strong rather than complete.

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 filler, and the core content (metrics, granularity, window) is front-loaded before the routing guidance to the sibling tool. Every clause 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?

An output schema exists, so return values need not be explained; annotations cover the safety profile; and the schema fully documents five parameters. The description supplies the granularity, window cap and routing context an agent needs to choose and call this tool 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 the schema already documents every parameter including hours, detail, project, service and environment. The description only echoes the hours window and bucket size, adding no syntax or default semantics beyond what the schema states. Baseline 3 applies.

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+resource plus the exact payload: requests, errors, p95 response time in 15-minute buckets with totals. It also explicitly distinguishes itself from tideways_get_performance by granularity and feature set, so an agent can separate the two 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 intents, and the second sentence names the alternative (tideways_get_performance) with the condition that selects it (per-minute detail, top transactions). This is explicit when-to-use plus a named alternative.

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

Deploy Server