Skip to main content
Glama

sit_down

Command the Unitree Go2 robot to sit down using natural language, which is translated into ROS2 instructions for precise execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.py:94-98 (handler)
    MCP tool handler and registration for 'sit_down'. It calls the WirelessController's sit_down method, stops the controller, and returns the message.
    @mcp.tool()
    def sit_down():
        _, msg = wirelesscontroller.sit_down()
        wirelesscontroller.stop()
        return msg
  • Core implementation of sit_down in WirelessController class. Stands up from a fall and publishes custom movement with keys=513 to make the robot sit down.
    def sit_down(self):
        self.stand_up_from_a_fall()
        return self._customised_movements(keys=513)
  • Helper method called by sit_down to stand up using specific keys before sitting.
    def stand_up_from_a_fall(self):
        return self._customised_movements(keys=1056)
  • Underlying helper that publishes WirelessController ROS2 messages with specified keys for custom robot movements.
    def _customised_movements(self, keys: int, rate: int = None, times: int = 5) -> tuple[bool, Any]:
        rate = rate if rate is not None else self.rate
        rate_opt = f"-r {rate} --times {times}"
        command = (
            f"source {self.setup_sh_path} && "
            f"ros2 topic pub {self.topic} {self.msg_type} "
            f"'{{lx: 0.0, ly: 0.0, rx: 0.0, ry: 0.0, keys: {keys}}}' {rate_opt}"
        )
        return self.execute(command)
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

  • @lpigeon/unitree-go2-mcp-server
  • @lpigeon/unitree-go2-mcp-server
  • @lpigeon/unitree-go2-mcp-server
  • @lpigeon/unitree-go2-mcp-server
  • @lpigeon/unitree-go2-mcp-server
  • @lpigeon/unitree-go2-mcp-server

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/lpigeon/unitree-go2-mcp-server'

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