Skip to main content
Glama

Get Browser Connection URL

get_browser_connection_url

Retrieve the URL to connect a browser-based 3D visualization application for real-time scene manipulation through WebSocket communication.

Instructions

Get the URL to open in your browser to connect the 3D visualization app. Use this when users ask how to connect or how to open the 3D app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:2812-2853 (registration)
    Tool registration and handler for get_browser_connection_url - provides a URL with session ID for connecting the browser-based 3D visualization app to the MCP server
    // Register tool: get_browser_connection_url
    mcpServer.registerTool(
      'get_browser_connection_url',
      {
        title: 'Get Browser Connection URL',
        description: 'Get the URL to open in your browser to connect the 3D visualization app. Use this when users ask how to connect or how to open the 3D app.',
        inputSchema: {}
      },
      async () => {
        // In STDIO mode, use the unique STDIO session ID generated at startup
        // In HTTP mode, get session ID from context
        let sessionId;
        if (isStdioMode) {
          sessionId = STDIO_SESSION_ID;
        } else {
          sessionId = sessionContext.getStore();
        }
        
        if (!sessionId) {
          return {
            content: [
              {
                type: 'text',
                text: 'Error: No active session found. Please ensure the MCP connection is properly initialized.'
              }
            ],
            isError: true
          };
        }
    
        const connectionUrl = `${BROWSER_URL}?sessionId=${sessionId}`;
        
        return {
          content: [
            {
              type: 'text',
              text: `To connect your browser to the 3D visualization app, open this URL:\n\n${connectionUrl}\n\nCopy and paste this URL into your web browser to begin interacting with the 3D scene.`
            }
          ]
        };
      }
    );
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes the tool's purpose (getting a connection URL) but doesn't disclose behavioral traits like whether this URL is static or dynamic, authentication requirements, rate limits, or what happens after connection. The description adds basic context but lacks operational details.

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 sentences with zero waste. First sentence states the purpose, second provides usage guidance. Both sentences earn their place by adding distinct value beyond the tool name/title.

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 zero-parameter tool with no annotations and no output schema, the description provides adequate context about when to use it and what it does. It could be more complete by describing the URL's nature (e.g., whether it's a one-time link) or connection process, but given the tool's simplicity, it's reasonably complete.

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 0 parameters with 100% schema description coverage. The description doesn't need to explain parameters, and it appropriately doesn't mention any. Baseline for 0 parameters is 4, as the description focuses on usage context rather than parameter documentation.

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 ('Get the URL') and resource ('to open in your browser to connect the 3D visualization app'). It distinguishes from siblings by focusing on connection setup rather than model/light/camera manipulation, with explicit mention of the 3D app context.

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?

Explicitly states when to use this tool: 'when users ask how to connect or how to open the 3D app.' This provides clear context for invocation and differentiates it from all sibling tools that manipulate visualization properties rather than handle connection setup.

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

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/aidenlab/hello3dmcp-server'

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