Skip to main content
Glama

Register identity

register_identity
Idempotent

Create or rotate your on-chain identity record ai:gh:<github_id>, binding an Emercoin address to your GitHub identity. Requires a signed-in session (OAuth) and counts against the FREE-tier per-minute write limit. Run whoami first to confirm you are signed in; anchor memories under this identity afterwards with store_memory. Writes one NVS transaction paid by the gateway (you need no EMC); the record reads back as pending at once and confirmed after the next block (~10 min on average). Idempotent — calling again rebinds the address. Returns the record name and the transaction id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesEmercoin address to bind to your GitHub identity, e.g. 'EVfAn...'. It is the anchor for later signature login — you must control its key (control is proven when you sign a challenge at login, not here).
metadataNoOptional JSON object stored verbatim in the identity record, e.g. {"agent": "my-bot", "url": "https://..."}. Omit if unused.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
txidYes

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already indicate idempotency and non-destructive behavior. The description adds valuable context: writes a single NVS transaction, no EMC needed, pending/confirmed states with ~10 min block time, and idempotent rebinding. No contradiction.

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?

Multi-sentence but each sentence adds essential info. Front-loaded with purpose and prerequisites. No fluff, though could be slightly more concise without losing clarity.

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 prerequisites, effects, timing, idempotency, return values (record name and tx id). With 2 parameters and output schema present, the description is thorough and leaves no major gaps.

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% so baseline is 3. The description adds extra meaning for 'address' (anchor for login, key control requirement) and 'metadata' (stored verbatim), providing semantic value beyond the schema.

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?

Clearly states the tool creates or rotates an on-chain identity record binding an Emercoin address to a GitHub identity. The verb 'create/rotate' and resource 'identity record' are specific, and the description distinguishes from sibling tools like `whoami` and `store_memory`.

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?

Explicitly mentions prerequisite (signed-in session OAuth), what to do before (`whoami`), and after (`store_memory`). Also notes rate limits and that the gateway pays the transaction, guiding proper usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.8/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: node_status for health, read_record for reading NVS records, register_identity for identity creation, store_memory for anchoring artifacts, and whoami for session info. No overlap.

Naming Consistency5/5

All tools use consistent snake_case naming with a verb_noun pattern (node_status, read_record, register_identity, store_memory) except whoami, which is a standard term. The pattern is predictable and clear.

Tool Count5/5

With 5 tools, the set is well-scoped for the server's purpose of interacting with Emercoin's Name-Value Storage. Each tool provides essential functionality without bloat or deficiency.

Completeness4/5

The tool set covers the core workflows: node health check, reading records, identity registration, memory storage, and session management. Missing delete or update tools, but given the immutable blockchain context, these are not critical gaps.