Skip to main content
Glama
sanchorelaxo

OpenSimulator MCP Server

by sanchorelaxo

run

Execute raw OpenSimulator console commands for region management, user administration, terrain editing, object manipulation, and HyperGrid operations not covered by other tools.

Instructions

Run any raw OpenSimulator console command. Use this for commands not covered by get/set categorization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'run' tool handler: an async function that takes a command string and sends it directly to the OpenSimulator console API via the global console instance.
    @mcp.tool()
    async def run(command: str) -> str:
        """
        Run any raw OpenSimulator console command.
        Use this for commands not covered by get/set categorization.
        """
        return await console.send_command(command)
  • The @mcp.tool() decorator registers the 'run' function as an MCP tool.
    @mcp.tool()
  • Function signature and docstring defining the input (command: str) and output (str), with description for schema generation.
    async def run(command: str) -> str:
        """
        Run any raw OpenSimulator console command.
  • The send_command method of OpenSimConsole class, which performs the actual HTTP requests to send the command and retrieve response.
    async def send_command(self, command: str) -> str:
        if not self.session_id:
            await self.start_session()
    
        async with await self._get_client() as client:
            response = await client.post(
                f"{self.base_url}/SessionCommand/",
                data={"ID": self.session_id, "COMMAND": command},
            )
            if response.status_code != 200:
                raise Exception(
                    f"Command failed: {response.status_code} - {response.text}"
                )
    
            # Wait for command to be processed before reading response
            await asyncio.sleep(0.3)
    
            read_response = await client.post(
                f"{self.base_url}/ReadResponses/{self.session_id}/"
            )
            return read_response.text
Behavior2/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 states the tool runs 'raw OpenSimulator console commands,' which implies it could execute any command, including potentially destructive or administrative ones, but doesn't disclose specific behavioral traits like safety risks, permission requirements, or rate limits. The description adds minimal context beyond the basic function.

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 two sentences with zero waste: the first states the purpose, and the second provides usage guidelines. It is front-loaded and appropriately sized, with every sentence earning its place by adding critical information.

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?

Given the tool's complexity (running arbitrary console commands) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers purpose and usage well, but lacks behavioral details like safety warnings or execution context, which are important for such a powerful tool with no annotations.

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

Parameters3/5

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

Schema description coverage is 0%, with one parameter 'command' undocumented in the schema. The description adds meaning by specifying it's for 'raw OpenSimulator console commands,' giving context to the parameter's purpose. However, it doesn't provide details on command syntax, examples, or constraints, so it partially compensates but not fully.

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 ('Run any raw OpenSimulator console command') and distinguishes it from siblings by mentioning 'commands not covered by get/set categorization.' It provides a verb+resource combination that is precise and differentiates from alternatives.

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?

The description explicitly states when to use this tool ('for commands not covered by get/set categorization') and implies when not to use it (for commands covered by get/set). It directly references sibling tools 'get' and 'set' as alternatives, providing clear contextual guidance.

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/sanchorelaxo/opensim-mcp'

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