Compare performance metrics of multiple robots over a specified time period to identify differences and optimize operations.
比较多个机器人的性能
参数:
- robot_ids: 机器人ID列表
- metric_columns: 比较指标列
- start_time: 开始时间戳
- end_time: 结束时间戳
返回:
- 比较结果| Name | Required | Description | Default |
|---|---|---|---|
| robot_ids | Yes | ||
| metric_columns | Yes | ||
| start_time | No | ||
| end_time | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description should cover behavioral traits. It only states 'returns comparison results' with no mention of side effects, safety, or read-only nature. Lacks details on error handling, limits, or permissions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is concise with a clear lead sentence and parameter list. The structure is front-loaded and wastes no words, though the parameter list duplicates schema information slightly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Lacks output schema and return details beyond 'comparison result'. Given 4 parameters and many siblings, more context is needed for an agent to use correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, requiring compensation. Description adds basic meanings for parameters (e.g., 'robot ID list', 'comparison metric columns'), but lacks types, formats, or constraints. Passes baseline but not enriching.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'compare performance of multiple robots', providing a specific verb and resource. It distinguishes from siblings like analyze_robot_data by focusing on multi-robot comparison, though not explicitly differentiating.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 analyze_robot_data or other performance tools. No exclusions or context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nonead/Nonead-Universal-Robots-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server