Tideways MCP Server

List Tideways projects

tideways_list_projects

Read-onlyIdempotent

Retrieves projects, scopes, and rate-limit status for your Tideways API token. Call this tool first to resolve unknown-project or scope errors before making API calls.

Instructions

List the projects, scopes and rate-limit status of the configured Tideways API token. Call this first when unsure which project to use, or after a scope or unknown-project error.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON 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 is shared by all projects of the token.
`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.

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?

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context about what is returned and when this tool helps recover from token/scope errors, though it does not describe pagination or output structure.

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 tightly written sentences front-load the purpose and then the usage trigger. Every sentence adds information without repetition or 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 an output schema present and no parameters, the description only needs to establish purpose and routing. It does that completely: what is listed, why it matters, and when to call it.

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?

The tool has zero parameters, so there are no parameter semantics to explain. The description appropriately focuses on the token context and result scope rather than inventing parameter details.

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?

The description states a specific verb and resource: list the projects, scopes, and rate-limit status available to the configured API token. That is enough to distinguish it from siblings such as tideways_list_services or tideways_get_performance.

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?

It gives clear trigger conditions: call this first when unsure which project to use, or after a scope or unknown-project error. It does not name a sibling alternative for cases where the project is already known, so it falls short of the explicit alternative-routing seen in a 5.

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

Deploy Server