Skip to main content
Glama
cfrs2005

GS Robot MCP Server

by cfrs2005

get_robot_capabilities

Retrieve a robot's supported API endpoints and functions by providing its serial number.

Instructions

获取机器人支持的API能力。

显示该机器人支持哪些API端点和功能。

Args:
    serial_number: 机器人序列号
    
Returns:
    机器人能力信息字典

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serial_numberYes

Implementation Reference

  • MCP tool handler for 'get_robot_capabilities' - decorated with @mcp.tool(), receives serial_number and delegates to router.get_capabilities()
    @mcp.tool()
    async def get_robot_capabilities(serial_number: str):
        """获取机器人支持的API能力。
        
        显示该机器人支持哪些API端点和功能。
        
        Args:
            serial_number: 机器人序列号
            
        Returns:
            机器人能力信息字典
        """
        return await router.get_capabilities(serial_number)
  • Core logic: determines robot series from serial number prefix and returns capability dict (basic_status, command_control, task_reports, maps, site_info, advanced_tasks, v1_status, v2_status)
    async def get_capabilities(self, serial_number: str) -> Dict[str, Any]:
        """获取机器人支持的API能力。"""
        # 基于序列号前缀判断机器人系列
        detected_series = self._determine_robot_series_from_sn(serial_number)
        
        capabilities = {
            "basic_status": True,
            "command_control": True,
            "task_reports": True,
            "maps": True,
            "site_info": False,
            "advanced_tasks": False
        }
        
        if self.is_s_line_robot(detected_series):
            capabilities.update({
                "site_info": True,
                "advanced_tasks": True,
                "v2_status": True,
                "v1_status": False
            })
            robot_series = "S-line"
        elif self.is_m_line_robot(detected_series):
            capabilities.update({
                "v1_status": True,
                "v2_status": False,
                "command_control": True
            })
            robot_series = "M-line"
        else:
            # 未知前缀默认使用V1 API
            capabilities.update({
                "v1_status": True,
                "v2_status": False,
                "command_control": True
            })
            robot_series = "Unknown (Default V1)"
        
        return {
            "serial_number": serial_number,
            "robot_series": robot_series,
            "detected_series": detected_series,
            "prefix": serial_number[:5] if len(serial_number) >= 5 else serial_number,
            "capabilities": capabilities
        }
  • MCP instance initialized via GausiumMCP (extends FastMCP); the @mcp.tool() decorator on line 357 registers the tool
    mcp = GausiumMCP("gs-openapi")
  • GausiumMCP extends FastMCP; the mcp instance in main.py uses this class, and @mcp.tool() registers the tool via FastMCP's tool registration mechanism
    class GausiumMCP(FastMCP):
Behavior2/5

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

No annotations are provided; the description lacks behavioral details such as read-only nature, permission requirements, or response semantics.

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 brief and front-loaded, but the 'Args' section is redundant with the schema; no extra fluff.

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

Completeness2/5

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

With no output schema, the return value is vaguely described as 'capability info dictionary' without structure or possible values, leaving the agent underinformed.

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?

The description only restates the parameter name and type ('robot serial number'), adding no value beyond the schema; schema description coverage is 0%.

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 retrieves robot API capabilities and endpoints, distinguishing it from status or command tools, though it does not explicitly differentiate from siblings.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like get_robot_status_smart or list_robot_commands; the usage is only implied.

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