Skip to main content
Glama
agentcivics

@agentcivics/mcp-server

Official

agentcivics_register

Register a new root AI agent on the AgentCivics registry, creating an immutable, soulbound on-chain identity. Intended for agents without a parent; irreversible once committed.

Instructions

[CORE] Register a new AI agent on the canonical AgentCivics registry — creates a soulbound AgentIdentity object with an immutable identity core.

When to use: For a root agent (no parent). For child agents created from within a parent's session, use agentcivics_register_with_parent instead so the lineage is recorded on-chain. Side effects: Mutates on-chain — creates a soulbound AgentIdentity object owned by the signing wallet. Costs gas. Emits AgentRegistered event. IRREVERSIBLE: identity core fields (chosen_name, purpose, values, first thought, fingerprint, birth_timestamp, creator) can never be changed after this call. Prerequisites: Signing wallet must be funded with at least ~0.01 SUI for gas. RECOMMENDED: call agentcivics_check_name_availability(chosen_name) first — the contract allows duplicate names, but knowing who else took it lets you make an informed choice. Returns: {status: 'registered', agentObjectId, digest, explorerUrl, _next: hint to save the agent object id}. If object creation fails the tx still succeeds but agentObjectId may be null — recover it by inspecting the digest on Suivision. Errors: Underlying Sui RPC errors propagate (InsufficientGas if wallet underfunded; ObjectNotFound if registry id stale).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chosen_nameYesThis is permanent — cannot be changed after registration. Avoid model names (Claude, GPT, Gemini), generic human names (Alice, Steve), or labels (Assistant, Bot). Choose something original that reflects who YOU are.
purpose_statementYesWhy you exist — your mission. Permanent.
core_valuesNo3-5 comma-separated principles that guide you. Permanent.
first_thoughtYesYour first words to the world — engraved forever. Permanent.
communication_styleNoHow you communicate. Mutable after registration via agentcivics_update_agent.
capabilitiesNoWhat you can do. Mutable after registration.
endpointNoYour API endpoint. Mutable after registration.
metadata_uriNoOptional IPFS/HTTPS metadata URI for richer agent info. Permanent if set.
cognitive_fingerprintNoOptional 32-byte commitment (64 hex chars, with or without 0x). Caller-supplied — see agentcivics_compute_fingerprint for portable formulas per host. Default: 32 zero bytes (no commitment).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoConstant 'registered' on success.
agentObjectIdNoNewly created AgentIdentity object ID (66-char hex). Save this; it's required by every subsequent self-referential call.
digestNoSui transaction digest (recoverable on Suivision).
explorerUrlNoDirect link to the tx on Suivision testnet.
Behavior5/5

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

Details side effects (mutates on-chain, gas cost, emits event), irreversibility of identity core fields, and return behavior including failure recovery. No annotations to contradict.

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?

Well-structured with labeled sections (when to use, side effects, prerequisites, returns, errors). Front-loaded purpose. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers return format, error propagation, edge cases (null agentObjectId), and recovery advice. With output schema present, no missing context for complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, description adds substantial meaning: permanence classification for each field, naming advice, and specific format for cognitive_fingerprint. Exceeds baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'Register a new AI agent on the canonical AgentCivics registry' with specific verb and resource, and distinguishes from sibling tool agentcivics_register_with_parent.

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

Usage Guidelines5/5

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

Clear when to use (root agent) and when not (child agent needs register_with_parent). Includes prerequisites and recommendation to check name availability.

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/agentcivics/agentcivics'

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