Skip to main content
Glama
nonead

nUR MCP Server

by nonead

get_joint_temperatures

Retrieve temperature readings in Celsius for all robot joints to monitor thermal conditions and prevent overheating during operation.

Instructions

获取指定IP机器人各关节的温度(摄氏度)。 IP:机器人地址

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes

Implementation Reference

  • The @mcp.tool() decorated handler function that implements get_joint_temperatures by calling JointTemperatures() on the UR robot model instance for the given IP, after checking connection.
    @mcp.tool()
    def get_joint_temperatures(ip: str):
        """获取指定IP机器人各关节的温度(摄氏度)。
        IP:机器人地址"""
        try:
            if '连接失败' in link_check(ip):
                return return_msg(f"与机器人的连接已断开。")
            logger.info(f"{robotModle_list[ip].JointTemperatures()}(摄氏度)")
            return return_msg(f"{robotModle_list[ip].JointTemperatures()}(摄氏度)")
        except Exception as e:
            logger.error(f"机器人各关节的温度获取失败: {str(e)}")
            return return_msg(f"机器人各关节的温度获取失败: {str(e)}")
  • The @mcp.tool() decorator registers this 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 the full burden. It states the tool retrieves temperature data, implying a read-only operation, but doesn't disclose behavioral traits such as whether it requires robot connection, has rate limits, returns real-time or historical data, or error handling. 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 appropriately sized with two concise sentences that front-load the purpose and parameter meaning. There is no wasted text, but it could be slightly more structured by separating usage notes. It efficiently conveys core information without redundancy.

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 covers the basic purpose and parameter semantics but lacks details on behavior, return values (e.g., format of temperature data), error cases, or integration with sibling tools. For a tool in a robotics context with many siblings, this leaves significant gaps for an AI agent.

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 meaning by specifying that the 'ip' parameter is the robot address, which clarifies its purpose beyond the schema's generic title 'Ip'. However, with 0% schema description coverage and only 1 parameter, the description compensates partially but doesn't detail format (e.g., IPv4, hostname) or constraints. Baseline is 4 for 0 parameters, but since there is 1 parameter, the score is adjusted to 3 for moderate value addition.

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 verb '获取' (get) and the resource '指定IP机器人各关节的温度' (temperatures of specified IP robot joints), specifying the unit as Celsius. It distinguishes from siblings like 'get_actual_joint_current' or 'get_actual_joint_voltage' by focusing on temperature. However, it doesn't explicitly differentiate from all siblings, such as 'analyze_robot_data', which might include temperature analysis.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions the IP parameter but doesn't specify prerequisites (e.g., robot connectivity), exclusions, or compare to similar tools like 'get_actual_joint_current' for other joint metrics. Usage is implied only by the parameter context.

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