Tideways MCP Server

List Tideways projects

tideways_list_projects

Read-onlyIdempotent

List the projects and scopes available to your Tideways API token and check the remaining hourly rate limit. Use this first when unsure which project to select or after scope errors.

Instructions

List the projects and scopes of the configured Tideways API token, and how much of the organization's hourly rate limit is left. Call this first when unsure which project to use, or after a scope or unknown-project error.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`scopes`	Yes	Token scopes: metrics (performance, summary, history), traces, errors (issues, observations)
`projects`	Yes
`rateLimit`	Yes	Rate-limit headers from the last counted request (null until another tool has made a request in this session; any data call, e.g. tideways_get_observations, fills it). The hourly limit depends on the Tideways plan and is shared by all tokens and projects of the organization.
`organization`	Yes	The token's organization (null if its projects span several)
`tokenExpired`	Yes
`defaultProject`	Yes	Project used when a call omits "project" (null if none can be chosen)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.1.1Oct 15, 2026

changedOutput schema / properties / rateLimit / description

Previous value: -"Rate-limit headers from the last counted request (null until another tool has made a request in this session; any data call, e.g. tideways_get_observations, fills it). The hourly limit is shared by all projects of the token."New value: +"Rate-limit headers from the last counted request (null until another tool has made a request in this session; any data call, e.g. tideways_get_observations, fills it). The hourly limit depends on the Tideways plan and is shared by all tokens and projects of the organization."

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, openWorld, and non-destructive, so the safety profile is covered. The description adds real context beyond that: results are limited to the caller's configured token scopes and include a rate-limit reading, which tells the agent why an empty or partial result may occur.

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?

One sentence for what it returns, one for when to call it, both front-loaded and free of filler. No sentence restates the name or annotations.

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 no elaboration. For a parameterless, read-only discovery tool the description covers purpose, invocation trigger, and the token-scoped nature of the result, leaving nothing material unstated.

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?

Zero parameters, so the schema carries no parameter semantics for the description to enrich. Baseline of 4 applies; nothing further is needed here.

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?

Names a specific verb (List) and resource (projects and scopes) scoped to the configured API token, plus a secondary payload (remaining hourly rate limit). This is clearly distinguishable from every sibling, which all operate on issues, services, traces, or performance data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit triggering conditions: call first when the right project is unknown, or after a scope or unknown-project error. It establishes precedence over other tools but does not name a specific alternative or state when not to call it.

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

Deploy Server