Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_workspaces_basic_info

Read-only

List your workspaces as id and name only to resolve workspace names to IDs for subsequent workspace-scoped calls.

Instructions

List every workspace you belong to, as id and name only. USE WHEN: The cheapest way to resolve a workspace name to an ID before a workspace-scoped call. Takes no arguments. USE INSTEAD: get_current_user if you need more than ids and names — but note that response is much larger, so prefer this one when ids suffice. EXAMPLE: {} RETURNS: Array of {id, name}. Nothing else, and no paging.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds useful behavioral details: 'Takes no arguments', 'Nothing else, and no paging', and emphasizes minimal cost. These go beyond the annotations and fully disclose the operation's scope.

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?

The description is tightly structured with USE WHEN, USE INSTEAD, EXAMPLE, and RETURNS sections. Every sentence adds value, the core purpose is front-loaded, and there is zero fluff.

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?

For a simple no-param read-only list tool, the description fully covers usage context, output shape, and exclusions (no paging). It also names the alternative, making it self-contained. Nothing an agent needs to call it correctly 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?

With zero parameters and 100% schema coverage, the description explicitly confirms 'Takes no arguments', removing any doubt. This is more than the baseline for zero-param tools.

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 clearly states the action ('List'), the resource ('every workspace you belong to'), and the exact output scope ('as id and name only'). It differentiates from siblings by focusing solely on workspace ID/name retrieval, and even names the alternative get_current_user.

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?

Provides explicit 'USE WHEN' context (cheapest way to resolve workspace name to ID) and an explicit 'USE INSTEAD' alternative (get_current_user) with trade-off rationale (response size). This leaves no ambiguity about when to choose this tool.

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

Deploy Server

Other Tools