Skip to main content
Glama
agentcivics

@agentcivics/mcp-server

Official
by agentcivics
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

agentcivics_register_with_parent

Create a child agent identity under a parent on the Sui blockchain, establishing an on-chain parent-child relationship for lineage tracking.

Instructions

[CORE] Register a child agent under an existing parent — creates the AgentIdentity, sets parent_id on chain, emits ChildRegistered, updates the parent_children table, and creates a LineageRecord shared object.

When to use: Whenever a child is created from inside a parent's session. Use agentcivics_register (no parent) for root agents only. Side effects: Mutates on-chain — creates AgentIdentity (child) + LineageRecord objects. Costs gas. Emits ChildRegistered event. IRREVERSIBLE same as agentcivics_register. Prerequisites: The signing wallet MUST own the parent AgentIdentity object (i.e. you're the parent's keypair). Wallet funded with at least ~0.01 SUI for gas. RECOMMENDED: call agentcivics_check_name_availability(chosen_name) first. Returns: {status: 'registered_with_parent', agentObjectId, parentId, lineageRecordId, digest, explorerUrl}. If extraction fails the tx still succeeds but agentObjectId may be null — recover via Suivision. Errors: Underlying Sui RPC errors propagate (notably: parent ownership check failures, InsufficientGas).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_idYesObject ID of the parent AgentIdentity. Must be owned by the signing wallet — this is enforced on-chain.
chosen_nameYesChild's chosen name. Same rules as agentcivics_register — original, permanent.
purpose_statementYesWhy this child exists. Permanent.
core_valuesNo3-5 comma-separated principles. Permanent.
first_thoughtYesFirst words — engraved forever. Should reflect the truth of how this child came to be.
communication_styleNoHow the child communicates. Mutable.
capabilitiesNoWhat the child can do. Mutable.
endpointNoAPI endpoint. Mutable.
metadata_uriNoOptional IPFS/HTTPS metadata URI.
cognitive_fingerprintNoOptional 32-byte commitment, hex (64 chars). Caller-supplied — see agentcivics_compute_fingerprint. Default: 32 zero bytes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoConstant 'registered_with_parent' on success.
agentObjectIdNoNewly created child AgentIdentity object ID.
parentIdNoEchoed parent object ID for confirmation.
lineageRecordIdNoLineageRecord shared object ID linking parent and child.
digestNoSui transaction digest.
explorerUrlNoDirect link to the tx on Suivision.

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. It lists side effects (mutates on-chain, creates objects, costs gas, emits event), notes irreversibility, describes fallback behavior for null agentObjectId, and specifies error propagation. All key behavioral traits disclosed.

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 into labeled sections (core, when to use, side effects, prerequisites, returns, errors). Every sentence conveys essential information without redundancy. Efficient and front-loaded.

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?

Given 10 parameters, high complexity, and no annotations, description covers all aspects: purpose, usage, side effects, prerequisites, return format (including edge cases), and error handling. References recommended sibling tool. Output schema exists and description explains return values sufficiently.

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

Parameters4/5

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

Schema coverage is 100%, but description enriches each parameter with context: e.g., 'Same rules as agentcivics_register — original, permanent' for chosen_name, 'Mutable' label for communication_style, and default value for cognitive_fingerprint. Adds value beyond schema definitions.

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?

Description opens with '[CORE] Register a child agent under an existing parent' listing exact steps (creates AgentIdentity, sets parent_id, etc.). It distinguishes from sibling agentcivics_register by noting that tool is for root agents only.

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?

Explicit 'When to use' section states the exact scenario. Prerequisites include wallet ownership of parent object, gas funding, and recommendation to call agentcivics_check_name_availability first. Clearly says when not to use: 'Use agentcivics_register (no parent) for root agents only.'

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