Tideways MCP Server

Get performance metrics

tideways_get_performance

Read-onlyIdempotent

Get performance totals, error rates, response-time percentiles, layer timings, top-impact transactions, and a timeline for any 1-1440 minute window ending at a chosen UTC time.

Instructions

Performance of any window of 1-1440 minutes ending at "end" (default now) within the last ~30 days: totals (requests, error rate, p95/median/average response time, time per layer), the top 20 transactions by impact, and a timeline. Older windows return zeros; use tideways_get_history for them. For 15-minute trends over 30 days use tideways_get_performance_summary.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`end`	No	Last minute included, "YYYY-MM-DD HH:mm" in UTC. Defaults to now.
`detail`	No	"concise" (default) returns a trimmed summary. "full" also includes the unmodified API response under "raw"; it can be very large.	concise
`minutes`	No	Window length in minutes (max 1440 = 24h). Above 60 the timeline is downsampled to at most 60 points.
`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
`project`	Yes
`criteria`	Yes	What Tideways actually queried. Times are UTC "YYYY-MM-DD HH:mm".
`timeline`	Yes
`transactions`	Yes	Top transactions by impact; the API returns at most 20

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, so the safety profile is covered structurally. The description adds genuinely new behavior: the ~30-day retention limit where older windows silently return zeros rather than erroring. It does not discuss auth or rate limits, but for a read tool with full annotation coverage that is acceptable.

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?

Two dense sentences, front-loaded with the core scope, then the returned data, then the routing constraints. No filler and nothing buried.

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 present (return shape need not be described), full annotation coverage, and 100% parameter documentation, the description only needs to add scope and routing — which it does completely for a 6-parameter read tool.

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 baseline is 3 and the schema already explains end, minutes, detail, project, service, and environment in detail. The description restates the window range and "end" default but adds no syntax or semantics beyond what the schema carries.

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?

Opens with a specific verb+resource+scope (performance metrics over a 1-1440 minute window ending at "end") and enumerates the payload: totals, top 20 transactions by impact, and a timeline. It explicitly differentiates itself from two named siblings, so an agent can route without opening a 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?

States both boundaries: windows older than ~30 days return zeros and should use tideways_get_history, while 15-minute trends over 30 days belong to tideways_get_performance_summary. This is explicit when-to-use and when-to-use-an-alternative guidance.

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

Deploy Server