Tideways MCP Server

List services

tideways_list_services

Read-onlyIdempotent

List a project's services (web, APIs, workers, CLI) named by open issues, default first. Use when a named app, API, worker, or transaction is missing from the default service.

Instructions

List the services of a project (web, APIs, workers, CLI) named by its open 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 3 requests, plus 1 per service searched: at most 30, and no more than a tenth of the hourly rate limit. Only services named by the newest open issues are listed; the Tideways UI service selector lists all.

Input Schema

TableJSON 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, and no more than a tenth of the hourly rate limit) 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

TableJSON Schema

Name	Required	Description
`search`	No	Present only with "search"
`project`	Yes
`services`	Yes	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.
`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.

First observedv2.0.0Oct 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/no-destructive, so the bar is lower, but the description goes further with a request-cost model ('Costs 3 requests, plus 1 per service searched: at most 30, and no more than a tenth of the hourly rate limit') and an important completeness caveat ('Only services named by the newest open issues are listed; the Tideways UI service selector lists all'). It omits nothing critical, though it doesn't mention error behavior for the environment (@schema covers that).

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?

Purpose and trigger are front-loaded, and every clause carries information (cost, caveat, ordering). It is dense and somewhat comma-chained ('..., with "search" set to one word of it: each service is searched...'), which costs a little readability, but no sentence is 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?

An output schema exists, so return values need not be explained, and the description still covers cost, ordering, default service, listing limitation, and trigger conditions. Nothing an agent needs in order to select and call this tool is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, and the description adds value beyond it by tying the search parameter to behavior: '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.' That explains why the parameter exists and how results are ranked, which the schema alone does not.

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 and scope: 'List the services of a project (web, APIs, workers, CLI) named by its open issues, the default service first.' This tells the agent exactly what comes back and in what order, and it names tideways_search_traces, so it is distinguishable from siblings.

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: '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.' It also names an alternative (the Tideways UI service selector) and explains how it differs, which is when-not guidance.

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

Deploy Server