Skip to main content
Glama
nonead

nUR MCP Server

by nonead

stop_data_recording

Terminates active data recording sessions for Universal Robots collaborative robots by specifying a session ID, ensuring controlled data collection management.

Instructions

停止数据记录

参数:
- session_id: 记录会话ID

返回:
- 停止状态

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes

Implementation Reference

  • The handler function for the 'stop_data_recording' tool, decorated with @mcp.tool() which registers it. It checks if the advanced data recorder is initialized, calls stop_recording on the given session_id, and returns success or failure message.
    @mcp.tool()
    def stop_data_recording(session_id: str):
        """
        停止数据记录
        
        参数:
        - session_id: 记录会话ID
        
        返回:
        - 停止状态
        """
        try:
            if advanced_data_recorder is None:
                return return_msg("高级数据记录器未初始化")
            
            # 停止记录
            success = advanced_data_recorder.stop_recording(session_id)
            
            if success:
                return return_msg({"success": True, "message": "数据记录已停止"})
            else:
                return return_msg({"success": False, "message": "停止数据记录失败,会话不存在"})
        except Exception as e:
            logger.error(f"停止数据记录失败: {str(e)}")
            return return_msg(f"停止数据记录失败: {str(e)}")
  • The @mcp.tool() decorator registers the stop_data_recording function as an MCP tool.
    @mcp.tool()
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 action ('stop data recording') but doesn't disclose behavioral traits like whether this is a destructive operation (likely yes, as it terminates recording), permission requirements, side effects (e.g., data saved or lost), or error conditions. The description is minimal and lacks critical operational context.

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 structured with sections for parameters and returns, using minimal words. However, the return section '返回: - 停止状态' (returns: - stop status) is vague and doesn't add value without an output schema. Overall, it's concise but could be more informative with its limited content.

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?

Given no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on behavior, parameters, returns, and usage context. For a tool that likely interacts with robot data recording (inferred from siblings), more information is needed to ensure safe and correct invocation.

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 lists 'session_id: 记录会话ID' (session_id: recording session ID), which adds basic meaning (identifies the session to stop). However, it doesn't explain format, source (e.g., from 'start_data_recording'), or constraints, leaving the parameter poorly documented. With one parameter and low coverage, this is inadequate.

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 '停止数据记录' (stop data recording), which is a clear verb+resource combination that matches the tool name. However, it doesn't differentiate from sibling tools like 'start_data_recording' beyond the obvious directional difference, nor does it specify what type of data recording is being stopped (robot data, performance metrics, etc.). The purpose is understandable but lacks specificity about the resource scope.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., that data recording must be active via 'start_data_recording'), exclusions, or contextual triggers. The agent must infer usage from the tool name alone, which is insufficient for optimal selection.

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/nonead/nUR-MCP-SERVER'

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