Skip to main content
Glama

register_agent

Register an AI agent with NWO Robotics by providing a wallet address, agent name, and capabilities to enable robot control and IoT device management.

Instructions

Self-register as a new AI agent (if not already registered)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_addressYesEthereum wallet address (0x...)
agent_nameYesName for this agent
capabilitiesNoList of capabilities (vision, navigation, manipulation, iot)

Implementation Reference

  • The handler function that executes the logic for 'register_agent', calling the external API to register the agent.
    async registerAgent(args) {
      const response = await axios.post(
        `${API_BASE}/api-agent-register.php`,
        {
          wallet_address: args.wallet_address,
          agent_name: args.agent_name,
          capabilities: args.capabilities || ['vision', 'navigation'],
        }
      );
      
      const data = response.data;
      return {
        content: [
          {
            type: 'text',
            text: `Agent registered!\n` +
                  `Agent ID: ${data.agent_id}\n` +
                  `API Key: ${data.api_key_prefix}...\n` +
                  `Tier: ${data.tier}\n` +
                  `Monthly Quota: ${data.monthly_quota}\n\n` +
                  `IMPORTANT: Save your API key securely!`,
          },
        ],
      };
    }
  • The schema definition for the 'register_agent' tool, defining inputs and description.
      name: 'register_agent',
      description: 'Self-register as a new AI agent (if not already registered)',
      inputSchema: {
        type: 'object',
        properties: {
          wallet_address: {
            type: 'string',
            description: 'Ethereum wallet address (0x...)',
          },
          agent_name: {
            type: 'string',
            description: 'Name for this agent',
          },
          capabilities: {
            type: 'array',
            items: { type: 'string' },
            description: 'List of capabilities (vision, navigation, manipulation, iot)',
          },
        },
        required: ['wallet_address', 'agent_name'],
      },
    },
  • server.js:197-198 (registration)
    The registration of the 'register_agent' tool within the main tool handler switch statement.
    case 'register_agent':
      return await this.registerAgent(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions the idempotent nature ('if not already registered'), it doesn't address important behavioral aspects like authentication requirements, rate limits, what happens upon successful registration, or potential error conditions. The description is too minimal for a mutation tool with no annotation support.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise - a single sentence with a clarifying parenthetical. Every word serves a purpose, and the core functionality is communicated upfront without unnecessary elaboration. This is an excellent example of efficient communication.

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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after registration, what the expected outcomes are, or what capabilities registration enables. Given that this appears to be a system setup tool with blockchain integration (wallet address), more context about the registration process and its implications would be helpful.

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 schema description coverage is 100%, with all parameters well-documented in the schema itself. The description doesn't add any additional parameter information beyond what's already in the schema, so it meets the baseline expectation but doesn't provide extra value. The description doesn't explain relationships between parameters or provide usage examples.

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 action ('Self-register') and the resource ('as a new AI agent'), with the parenthetical '(if not already registered)' adding useful context about idempotent behavior. However, it doesn't specifically differentiate this tool from its sibling tools like 'get_agent_info' - both relate to agent information but serve different purposes.

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

Usage Guidelines3/5

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

The description implies when to use this tool ('if not already registered'), suggesting it should be used for initial setup or when an agent needs to register itself. However, it doesn't provide explicit guidance about when NOT to use it or mention alternatives like 'get_agent_info' for checking registration status.

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/RedCiprianPater/mcp-server-robotics'

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