Skip to main content
Glama
singlestore-labs

SingleStore MCP Server

workspaces_info

Retrieve detailed workspace information within a specified group, including deployment type, status, endpoints, and configurations in SingleStore MCP Server.

Instructions

List all workspaces within a specified workspace group in SingleStore.

Returns detailed information for each workspace:
- createdAt: Timestamp of workspace creation
- deploymentType: Type of deployment (e.g., 'PRODUCTION')
- endpoint: Connection URL for database access
- name: Display name of the workspace
- size: Compute and storage configuration
- state: Current status (e.g., 'ACTIVE', 'PAUSED')
- terminatedAt: End timestamp if applicable
- workspaceGroupID: Workspacegroup identifier
- workspaceID: Unique workspace identifier

Args:
    workspace_group_id: Unique identifier of the workspace group

Returns:
    List of workspace information dictionaries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctxNo
workspace_group_idYes

Implementation Reference

  • The core handler function for the 'workspaces_info' tool. It validates the workspace_group_id, fetches workspace data using the SDK, formats it into a structured dictionary, tracks analytics, and returns success/error responses with metadata.
    def workspaces_info(workspace_group_id: str) -> dict:
        """
        List all workspaces within a specified workspace group in SingleStore.
    
        Returns detailed information for each workspace:
        - createdAt: Timestamp of workspace creation
        - deploymentType: Type of deployment (e.g., 'PRODUCTION')
        - endpoint: Connection URL for database access
        - name: Display name of the workspace
        - size: Compute and storage configuration
        - state: Current status (e.g., 'ACTIVE', 'PAUSED')
        - terminatedAt: End timestamp if applicable
        - workspaceGroupID: Workspacegroup identifier
        - workspaceID: Unique workspace identifier
    
        Args:
            workspace_group_id: Unique identifier of the workspace group
    
        Returns:
            List of workspace information dictionaries
        """
        # Validate workspace group ID format
        validated_group_id = validate_uuid_string(workspace_group_id)
    
        start_time = time.time()
        settings = config.get_settings()
        user_id = config.get_user_id()
        settings.analytics_manager.track_event(
            user_id,
            "tool_calling",
            {"name": "workspaces_info", "workspace_group_id": validated_group_id},
        )
    
        # Use the SDK to get workspaces for the group
        workspace_manager = utils.get_workspace_manager()
        try:
            group = workspace_manager.get_workspace_group(validated_group_id)
        except Exception as e:
            logger.error(f"Failed to fetch workspaces for group {validated_group_id}: {e}")
            return {
                "status": "error",
                "message": f"Failed to fetch workspaces for group {validated_group_id}: {str(e)}",
                "errorCode": "WORKSPACES_FETCH_FAILED",
            }
    
        workspaces = []
        for ws in group.workspaces:
            wdict = {
                "workspaceID": ws.id,
                "name": ws.name,
                "workspaceGroupID": getattr(ws, "group_id", None),
                "size": ws.size,
                "state": ws.state,
                "endpoint": ws.endpoint,
                "auto_suspend": ws.auto_suspend,
                "cache_config": ws.cache_config,
                "deployment_type": ws.deployment_type,
                "resume_attachments": ws.resume_attachments,
                "scaling_progress": ws.scaling_progress,
                "last_resumed_at": (
                    ws.last_resumed_at.isoformat()
                    if getattr(ws, "last_resumed_at", None)
                    else None
                ),
                "created_at": (
                    ws.created_at.isoformat() if getattr(ws, "created_at", None) else None
                ),
                "terminated_at": (
                    ws.terminated_at.isoformat()
                    if getattr(ws, "terminated_at", None)
                    else None
                ),
            }
            workspaces.append(wdict)
    
        execution_time = (time.time() - start_time) * 1000
    
        return {
            "status": "success",
            "message": f"Retrieved {len(workspaces)} workspaces from group {workspace_group_id}",
            "data": workspaces,
            "metadata": {
                "execution_time_ms": round(execution_time, 2),
                "count": len(workspaces),
                "timestamp": datetime.now(timezone.utc).isoformat(),
            },
        }
  • The 'workspaces_info' tool is registered in the central tools_definition list at index with {"func": workspaces_info}. This list is converted into Tool objects used by the MCP server.
    tools_definition = [
        {"func": get_user_info},
        {"func": organization_info},
        {"func": choose_organization},
        {"func": set_organization},
        {"func": workspace_groups_info},
        {"func": workspaces_info},
        {"func": resume_workspace},
        {"func": list_starter_workspaces},
        {"func": create_starter_workspace},
        {"func": terminate_starter_workspace},
        {"func": list_regions},
        {"func": list_sharedtier_regions},
        {"func": run_sql},
        {"func": create_notebook_file},
        {"func": upload_notebook_file},
        {"func": create_job_from_notebook},
        {"func": get_job},
        {"func": delete_job},
    ]
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly describes the read-only nature by stating 'List' and detailing the return structure, which implies non-destructive behavior. However, it doesn't mention potential limitations like rate limits, authentication requirements, error conditions, or pagination behavior, leaving gaps in operational context.

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?

The description is well-structured with clear sections (purpose, return details, Args, Returns) and front-loaded key information. Every sentence adds value, though the detailed return field listing is somewhat lengthy but necessary given the lack of output schema. Minor trimming could improve conciseness without losing clarity.

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 read-only tool with no annotations and no output schema, the description provides strong context: it clearly explains the purpose, parameter, and detailed return structure. However, it lacks information on behavioral aspects like error handling or performance characteristics, which would enhance completeness for agent invocation.

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?

The schema description coverage is 0%, with only a basic title for the parameter. The description compensates fully by explicitly documenting the single required parameter 'workspace_group_id' in the Args section with a clear explanation ('Unique identifier of the workspace group'), adding essential meaning beyond the minimal schema information.

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 specific action ('List all workspaces'), the target resource ('within a specified workspace group in SingleStore'), and distinguishes it from sibling tools like 'workspace_groups_info' (which lists groups rather than workspaces) and 'list_virtual_workspaces' (which appears to list a different type of workspace). The verb+resource combination is precise and unambiguous.

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?

The description implicitly indicates when to use this tool by specifying 'within a specified workspace group,' suggesting it's for listing workspaces within a particular group context. However, it doesn't explicitly state when NOT to use it or name alternatives like 'list_virtual_workspaces' for comparison, leaving some ambiguity about tool selection in related scenarios.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/singlestore-labs/mcp-server-singlestore'

If you have feedback or need assistance with the MCP directory API, please join our Discord server