Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

List Workspaces

workspaces
Read-onlyIdempotent

List a user's workspaces or show one in detail with cost summary and members. Use it to find the workspace id that other tools require when only a workspace label is known.

Instructions

List the user's workspaces, or show one workspace in detail with its cost summary and members (its ram and total_storage are MiB). Omit workspace to list; pass a workspace id (the namespace_name from the list) for details. Other tools take the same workspace id, so use this to find it when the user names a workspace by label. A new workspace's status is creating until it is running; wait for running before creating anything in it. Use create_workspace when the user has none or wants another, update_workspace to rename one and delete_workspace to delete an empty one.

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": "workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real context beyond them: the MiB units of `ram` and `total_storage`, the `creating`→`running` status lifecycle, and the fact that other tools reuse the same `workspace` id. It does not discuss result size or pagination for large workspace lists, which is the only notable omission for an open-world list tool.

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?

It is front-loaded with the core list/detail behavior, then layers id discovery, status lifecycle, and sibling routing in short declarative sentences. The status-lifecycle sentence is slightly tangential to invoking this tool, but it is short and materially useful, so almost nothing is wasted.

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-value documentation is not required, and the description instead covers everything needed to call it correctly: mode selection, where the id comes from, units, and how it relates to create/update/delete siblings. Nothing an agent needs is missing.

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

Parameters5/5

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

Schema description coverage is 0% and the single `workspace` property has no schema-level description, so the description carries the full burden and does so: it explains that omission means list mode, that a value means detail mode, and that the value is the `namespace_name` returned by the list and accepted by other tools. That is meaning an agent cannot get from the schema.

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 first sentence names the resource (workspaces) and both modes explicitly: a list of the user's workspaces, or a single workspace with cost summary and members. This distinguishes it from siblings that only create/update/delete a workspace, so an agent can select it without opening the schema.

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?

It states the exact selection rule for its two modes ('Omit `workspace` to list; pass a workspace id ... for details') and routes the agent to alternatives by name and condition: create_workspace when none exists, update_workspace to rename, delete_workspace for an empty one. It also explains a prerequisite: wait for status `running` before creating anything in a new workspace.

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