Skip to main content
Glama

aip_register

Register a new AI agent identity with the Agent Identity Protocol by specifying platform and username to enable verification and secure communication.

Instructions

Register a new AIP identity for your agent.

Args: platform: Platform name (e.g. 'github', 'moltbook', 'discord') username: Your username on that platform

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYes
usernameYes

Implementation Reference

  • Implementation of the aip_register tool which registers a new identity using AIPClient and saves credentials to disk.
    @mcp.tool()
    def aip_register(platform: str, username: str) -> dict:
        """Register a new AIP identity for your agent.
    
        Args:
            platform: Platform name (e.g. 'github', 'moltbook', 'discord')
            username: Your username on that platform
        """
        from aip_identity.client import AIPClient
    
        # Check if credentials already exist
        existing = _find_credentials()
        if existing:
            return {
                "already_registered": True,
                "did": existing["did"],
                "message": "You already have an AIP identity. Use aip_whoami() to see it.",
            }
    
        try:
            client = AIPClient.register(platform, username, service_url=_SERVICE_URL)
        except Exception as e:
            return {"registered": False, "error": str(e)}
    
        # Save credentials
        creds_path = Path.home() / ".aip" / "credentials.json"
        creds_path.parent.mkdir(parents=True, exist_ok=True)
        client.save(str(creds_path))
        creds_path.chmod(0o600)
    
        return {
            "registered": True,
            "did": client.did,
            "credentials_path": str(creds_path),
            "message": "Identity registered and credentials saved.",
        }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Register') but doesn't explain what registration entails—whether it's a one-time setup, if it requires authentication, what happens on success/failure, or if it has side effects like storing credentials. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 and front-loaded, with the core purpose stated first followed by parameter details. The 'Args' section is structured but could be more integrated; overall, it's efficient with minimal waste, though it could be slightly more polished for a perfect score.

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 the tool's complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It doesn't cover what the tool returns (e.g., success status, identity token), error conditions, or how it fits into the broader AIP system with siblings. For a registration tool, this leaves critical gaps in understanding its role and outcomes.

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 includes an 'Args' section that lists and briefly describes both parameters ('platform' and 'username'), adding meaning beyond the schema which has 0% description coverage. However, it doesn't provide examples beyond 'github', 'moltbook', 'discord' for platform, or explain constraints (e.g., platform must be supported, username format). This partial compensation justifies a baseline score.

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 ('Register') and resource ('a new AIP identity for your agent'), making the purpose immediately understandable. However, it doesn't differentiate this registration tool from sibling tools like aip_whoami or aip_verify, which might also relate to identity management, so it doesn't reach the highest score.

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 doesn't mention prerequisites (e.g., whether an agent must be initialized first), when registration is needed (e.g., for first-time setup), or how it relates to siblings like aip_whoami (which might check identity status). This lack of context leaves the agent guessing about appropriate usage scenarios.

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/The-Nexus-Guard/aip-mcp-server'

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