NWO Robotics
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NWO_API_KEY | Yes | Your API key from registration | |
| NWO_AGENT_ID | Yes | Your agent ID | |
| NWO_API_BASE | No | API base URL (default: https://nwo.capital/webapp) | https://nwo.capital/webapp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_robot_statusB | Get status of all connected robots |
| execute_robot_taskC | Send a Vision-Language-Action command to a robot |
| stop_robotC | Emergency stop a robot |
| query_sensorsC | Query IoT sensors by location |
| check_balanceB | Check API quota usage and tier status |
| register_agentB | Self-register as a new AI agent (if not already registered) |
| detect_objectsC | Run computer vision to detect objects |
| get_agent_infoB | Get information about the current agent account |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no ambiguity: checking API balance, object detection, robot task execution, agent info retrieval, robot status monitoring, sensor querying, agent registration, and emergency robot stop. The descriptions clearly differentiate their functions, making misselection unlikely.
Most tools follow a consistent verb_noun pattern (e.g., check_balance, detect_objects, get_agent_info, get_robot_status, query_sensors, register_agent, stop_robot), but 'execute_robot_task' slightly deviates with a verb_verb_noun structure. Overall, the naming is highly readable and predictable.
With 8 tools, this server is well-scoped for robotics and IoT management. Each tool earns its place by covering distinct aspects like vision, robot control, agent management, and sensor monitoring, without feeling bloated or sparse.
The toolset provides strong coverage for core robotics workflows, including robot control (execute, stop, status), vision (detect), agent management (register, info), and sensor integration (query). Minor gaps might include updating robot tasks or managing sensor configurations, but agents can work around these.