Skip to main content
Glama
sanchorelaxo

OpenSimulator MCP Server

by sanchorelaxo

get

Retrieve information from OpenSimulator servers using console commands to show version, uptime, regions, users, or monitoring reports.

Instructions

Run a read-only/info/show style command.

Examples:

  • show version

  • show uptime

  • show regions

  • show users full

  • monitor report

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYes
argsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the MCP tool named 'get'. It constructs a command string and sends it to the OpenSimulator console via the global 'console' instance for read-only operations.
    @mcp.tool()
    async def get(command: str, args: str = "") -> str:
        """
        Run a read-only/info/show style command.
    
        Examples:
        - show version
        - show uptime
        - show regions
        - show users full
        - monitor report
        """
        return await console.send_command(_build_command(command, args))
  • Helper function used by the 'get' tool (and others) to build the full console command from base command and optional arguments.
    def _build_command(base: str, args: str = "") -> str:
        base = base.strip()
        args = args.strip()
        return f"{base} {args}".strip()
  • Core helper method in OpenSimConsole class that sends the command to the REST API, manages session, and retrieves the response. Called by the 'get' tool.
    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
  • The @mcp.tool() decorator registers the 'get' function as an MCP tool.
    @mcp.tool()
    async def get(command: str, args: str = "") -> str:
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the read-only behavioral trait, which is helpful. However, it doesn't mention authentication needs, rate limits, error handling, or output format. The examples hint at command patterns but lack full behavioral context like what 'monitor report' entails.

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 appropriately sized with a clear opening statement followed by examples. Every sentence earns its place by providing essential information and practical guidance. However, the examples could be more tightly integrated with the main description for better flow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema, the description doesn't need to explain return values. However, with no annotations, 0% schema coverage, and 2 parameters, the description is incomplete—it lacks details on parameter usage, system context, and behavioral constraints. The examples help but don't fully compensate for the gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It provides no explicit information about the 'command' or 'args' parameters beyond the examples. The examples imply possible values but don't explain parameter roles, formats, or constraints. This leaves significant gaps in understanding how to use the parameters effectively.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool runs 'read-only/info/show style commands', which gives a general purpose but lacks specificity about what resource or system it operates on. It distinguishes from siblings 'run' and 'set' by emphasizing read-only nature, but doesn't explicitly name what it retrieves. The examples provide concrete patterns but don't define scope.

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 clearly indicates this is for read-only operations through the phrase 'read-only/info/show style command', which implicitly suggests when to use it versus write operations. However, it doesn't explicitly name alternatives like 'run' or 'set' or provide exclusion criteria. The examples offer practical guidance but no explicit when-not-to-use statements.

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