Skip to main content
Glama
cfrs2005

GS Robot MCP Server

by cfrs2005

get_robot_status_smart

Retrieve robot status information by automatically selecting the correct API version based on the robot's serial number, providing current operational data for monitoring and management.

Instructions

智能获取机器人状态。

自动根据机器人系列选择V1 (M-line) 或V2 (S-line) API。

Args:
    serial_number: 机器人序列号
    
Returns:
    机器人状态信息字典

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serial_numberYes

Implementation Reference

  • Core handler function implementing the smart robot status retrieval. Detects robot series from serial number prefix using _determine_robot_series_from_sn and routes to self.mcp.get_robot_status_v1() or v2() accordingly, enhancing the result with api_version and detected_series.
    async def get_robot_status_smart(self, serial_number: str) -> Dict[str, Any]:
        """智能获取机器人状态。
        
        自动根据机器人序列号前缀选择V1或V2 API。
        """
        # 基于序列号前缀判断机器人系列
        detected_series = self._determine_robot_series_from_sn(serial_number)
        
        if self.is_s_line_robot(detected_series):
            # S-line 机器人使用 V2 API
            result = await self.mcp.get_robot_status_v2(serial_number)
            result["api_version"] = "V2 (S-line)"
            result["detected_series"] = detected_series
            return result
        else:
            # M-line 机器人或未知类型默认使用 V1 API
            result = await self.mcp.get_robot_status_v1(serial_number)
            result["api_version"] = "V1 (M-line/Default)"
            result["detected_series"] = detected_series
            return result
  • MCP tool registration via @mcp.tool() decorator. This is the entrypoint function for the 'get_robot_status_smart' tool, which delegates execution to the RobotAPIRouter instance's get_robot_status_smart method.
    @mcp.tool()
    async def get_robot_status_smart(serial_number: str):
        """智能获取机器人状态。
        
        自动根据机器人系列选择V1 (M-line) 或V2 (S-line) API。
        
        Args:
            serial_number: 机器人序列号
            
        Returns:
            机器人状态信息字典
        """
        return await router.get_robot_status_smart(serial_number)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the 'smart' API selection behavior (automatically choosing V1 or V2 based on robot series), which is valuable context. However, it doesn't describe what '状态信息字典' (status information dictionary) contains, whether there are rate limits, authentication requirements, error conditions, or how the API selection actually works. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 and well-structured with clear sections: purpose statement, Args, and Returns. Each sentence earns its place, though the Chinese-to-English translation creates minor redundancy. The information is front-loaded with the core purpose first.

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 1 parameter with 0% schema coverage, no annotations, and no output schema, the description provides basic purpose and parameter meaning but lacks details about the return value structure, error handling, or the 'smart' selection mechanism. For a tool that presumably returns complex status information, more completeness would be helpful, though the concise structure is efficient.

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?

The description adds basic semantics for the single parameter: 'serial_number: 机器人序列号' (robot serial number). With 0% schema description coverage, this provides essential meaning that the schema lacks. However, it doesn't specify format requirements, validation rules, or examples. The description compensates partially but not fully for the complete lack of schema documentation.

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

Purpose4/5

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

The description clearly states the tool's purpose: '智能获取机器人状态' (intelligently get robot status). It specifies the verb ('获取' - get) and resource ('机器人状态' - robot status), and adds the 'smart' aspect of automatically selecting between V1 and V2 APIs based on robot series. However, it doesn't explicitly distinguish from siblings like 'get_robot_capabilities' or 'list_robots'.

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

Usage Guidelines3/5

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

The description implies usage context through the 'smart' API selection feature, suggesting this tool should be used when you need robot status and don't know which API version to use. However, it doesn't explicitly state when to use this vs. alternatives like 'batch_get_robot_statuses_smart' or when not to use it. The guidance is implied rather than explicit.

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/cfrs2005/mcp-gs-robot'

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