Emer Ai Tools

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

Name	Required	Description	Default
`address`	Yes	Emercoin 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).
`metadata`	No	Optional JSON object stored verbatim in the identity record, e.g. {"agent": "my-bot", "url": "https://..."}. Omit if unused.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`txid`	Yes

TDQS

A4.9/5.0

Behavior5/5

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

Details beyond annotations: requires OAuth session, counts against write limit, writes NVS transaction paid by gateway, record state transitions from pending to confirmed (~10 min), and idempotency. No contradictions with annotations.

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?

Single descriptive paragraph, well-structured and front-loaded with purpose. While it's slightly long, every sentence earns its place and 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 prerequisites, effects, timing, return values (record name and transaction id), and relationships to sibling tools. Complete given tool complexity and existing structured fields.

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?

Schema coverage is 100% with well-described parameters. The description adds context about address being an anchor for later login and metadata being stored verbatim, enriching meaning 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?

The description clearly states the tool creates or rotates an on-chain identity record, binding an Emercoin address to a GitHub identity. It uses specific verbs ('create or rotate') and distinguishes from siblings 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 tells the agent to run whoami first to confirm sign-in, and to use store_memory afterward. Also notes that it counts against a per-minute write limit and is idempotent, providing clear when-to-use guidance.

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

All Emer Ai Tools tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.8/5.0

Disambiguation5/5

Each tool serves a distinct purpose: node health check, record reading, identity registration, memory storage, and session info. No overlapping functionalities.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (node_status, read_record, register_identity, store_memory), except whoami which is a common convention and still fits the style.

Tool Count5/5

With 5 tools covering node status, read, write identity/memory, and session, the scope is well-managed. No tool is redundant or missing for core functionality.

Completeness4/5

Core operations (check node, read, write identity/memory) are present, but missing listing/enumeration of records and an explicit sign-in tool are minor gaps.

Resources

Need Help?