OpenUptime

list_workspaces

Read-onlyIdempotent

Discover accessible workspaces and their project IDs before calling private tools, then use those IDs to select a scope or rely on connection defaults.

Instructions

Discover the workspace and project ids this connection may use before calling private tools. Returns accessible workspaces with their projects; it does not list other users' workspaces. Pass workspace/project ids to private tools to select a scope, or omit them to use this connection's defaults.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_workspaces"
  }
}

Input Schema

Name	Required	Description	Default
`project`	No	Project id (from list_workspaces). Omit to use the default project of the workspace.
`workspace`	No	Workspace id (from list_workspaces). Omit to use the default one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds scope semantics beyond that: results are limited to this connection's accessible workspaces, and omitted parameters fall back to connection defaults. It does not describe result shape or pagination, keeping it below a 5.

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?

Three sentences, front-loaded with the purpose and the pre-condition, then the return content, then the parameter guidance. Nothing redundant and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, zero-required, read-only discovery tool with rich annotations, the description covers purpose, scope, and default behavior adequately. With no output schema, it does briefly characterize the return ('accessible workspaces with their projects'), though it does not describe the shape of nested project data.

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 both parameters are already documented (including 'from list_workspaces' provenance and omit-to-default). The description reinforces the omission behavior ('omit them to use this connection's defaults'), adding light but real meaning on top of the schema, so it edges above the baseline 3.

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 opens with a specific verb and resource ('Discover the workspace and project ids') and states exactly what is returned ('accessible workspaces with their projects'). It also draws a clear boundary ('it does not list other users' workspaces'), which no sibling tool covers, so an agent can distinguish it from create_workspace or list_monitors.

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 explicit ordering guidance ('before calling private tools') and explains both invocation modes: pass ids to select a scope, or omit them to use this connection's defaults. It does not name an alternative tool for any overlapping need, so it stops short of full when/when-not routing.

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