Tideways MCP Server

List services

tideways_list_services

Read-onlyIdempotent

List a Tideways project's services (web, APIs, workers, CLI), default first, and search their traces by one word to find the service handling an app, API, worker, or missing transaction.

Instructions

List the services of a project (web, APIs, workers, CLI) named by its issues, the default service first. Call it when the user names an app, API or worker that is not a project, or a transaction that tideways_search_traces does not find in the default service, with "search" set to one word of it: each service is searched for that word and the services are sorted by matching traces, so the first ones serve it. Costs 4 requests, plus 1 per service searched: at most 30, fewer when the hourly rate limit is small or nearly used up. Only services named by the newest open or ignored issues are listed; the Tideways UI service selector lists all.

Input Schema

Name	Required	Description
`search`	No	One whole word of the app, API, worker or transaction to find (e.g. "voucher"). Searches the traces of each service for it (one request per service: at most 30 services, fewer when the hourly rate limit is small or nearly used up) and sorts the services by matching traces.
`project`	No	Tideways project as "project" or "organization/project". Defaults to the defaultProject that tideways_list_projects reports; call it for valid names.
`environment`	No	Environment, e.g. "production" or "staging". Defaults to the configured environment, else production; "environment" in the result shows which was used. When results come back, an unknown name fails with an error.

Output Schema

Name	Required	Description
`search`	No	Present only with "search"
`project`	Yes
`services`	Yes	Services named by the newest open or ignored errors, slow SQL queries and deprecations of all services (first page of each), plus the default service; other services are missing, and the Tideways UI service selector lists all. Sorted default first, then by issues; with "search", by matchingTraces.
`environment`	Yes	Environment whose issues were read
`defaultService`	Yes	The project's default service, read when no service is passed or configured

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.1.1Oct 15, 2026

changedInput schema / properties / search / description

Previous value: -"One whole word of the app, API, worker or transaction to find (e.g. \"voucher\"). Searches the traces of each service for it (one request per service: at most 30 services, and no more than a tenth of the hourly rate limit) and sorts the services by matching traces."New value: +"One whole word of the app, API, worker or transaction to find (e.g. \"voucher\"). Searches the traces of each service for it (one request per service: at most 30 services, fewer when the hourly rate limit is small or nearly used up) and sorts the services by matching traces."

changedOutput schema / properties / search / properties / notSearched / description

Previous value: -"Services left out: one call searches at most 30 services, no more than a tenth of the hourly rate limit, and keeps 10 requests in reserve; search them with tideways_search_traces"New value: +"Services left out: one call searches at most 30 services, stays within a tenth of the hourly rate limit and keeps 10 requests in reserve; search them with tideways_search_traces"

changedOutput schema / properties / services / description

Previous value: -"Services named by the newest open errors, slow SQL queries and deprecations (first page of each), plus the default service; other services are missing, and the Tideways UI service selector lists all. Sorted default first, then by issues; with \"search\", by matchingTraces."New value: +"Services named by the newest open or ignored errors, slow SQL queries and deprecations of all services (first page of each), plus the default service; other services are missing, and the Tideways UI service selector lists all. Sorted default first, then by issues; with \"search\", by matchingTraces."

changedOutput schema / properties / services / items / properties / example / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "date": {
-        "description": "UTC \"YYYY-MM-DD HH:mm\"",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "transaction": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "url": {
-        "description": "Request URL without query string",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "transaction",
-      "url",
-      "date"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "date": {
+        "anyOf": [
+          {
+            "description": "\"YYYY-MM-DD HH:mm\"",
+            "pattern": "^\\d{4}-\\d{2}-\\d{2} \\d{2}:\\d{2}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "UTC \"YYYY-MM-DD HH:mm\""
+      },
+      "transaction": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "url": {
+        "description": "Request URL without query string",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "transaction",
+      "url",
+      "date"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / services / items / properties / issues / description

Previous value: -"How many of the open issues this call read name this service"New value: +"How many of the issues this call read (open and ignored) name this service"

First observedv2.0.0Oct 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (which already mark it read-only/idempotent) by disclosing cost (4 requests plus 1 per service, capped at 30, reduced under rate limits) and a real scope limitation: only services named by the newest open/ignored issues are listed, unlike the UI selector which lists all. This is the kind of behavior an agent needs before calling.

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?

The core purpose is front-loaded in the first sentence, and the cost and scope sentences each carry weight. Some phrasing is dense and slightly awkward ('named by its issues', 'so the first ones serve it'), but there is no filler.

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 a rich output schema already covering return values, the description completes the picture by covering when to use it, the search parameter's role, request cost, rate-limit behavior, and the listing-scope limitation. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the schema already documents all three parameters in detail, including search semantics and environment defaults. The description reinforces the search flow ('one word of it' → sorted by matching traces) but adds little beyond what the schema descriptions state; baseline 3 is appropriate.

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?

Specific verb+resource: it lists the services of a project, enumerating the kinds (web, APIs, workers, CLI) and noting the default service leads. It also distinguishes itself from siblings by contrasting with tideways_search_traces when the default service misses a transaction.

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?

Explicit trigger conditions are given: call it when the user names an app/API/worker that is not a project, or when tideways_search_traces fails to find a transaction in the default service. It names the alternative and the exact condition that selects this tool.

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

Deploy Server