Emer Ai Tools

This connector has been deprecated

Moved to com.steledger/gateway — same service, now at https://api.steledger.com/mcp

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 write limits (see whoami). 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 (about 8 minutes on average lately). Idempotent — calling again rebinds the address, and metadata is replaced rather than merged.

Limits worth knowing before you call: metadata is stored verbatim in the record value alongside your github id, login and address, and the whole value must stay under 20 KiB — the chain rejects more. Every 128 bytes of name plus value adds about 0.0001 EMC to the fee the gateway pays for you. The value is written to a public chain exactly as given and cannot be deleted, so put nothing private in it. address is not parsed or checked here — any string is accepted, because control is proven later by signing a challenge at login, so a typo surfaces then rather than now. 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
`quota`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 23, 2026

addedOutput schema / $defs

Added value: +{
+  "Quota": {
+    "description": "Writes this account has left on its tier. `writes_open_on` (a UTC date)\nappears only while the GitHub account is too new to write.",
+    "properties": {
+      "writes_left_this_minute": {
+        "title": "Writes Left This Minute",
+        "type": "integer"
+      },
+      "writes_left_today": {
+        "title": "Writes Left Today",
+        "type": "integer"
+      },
+      "writes_open_on": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Writes Open On"
+      }
+    },
+    "title": "Quota",
+    "type": "object"
+  }
+}

addedOutput schema / properties / quota

Added value: +{
+  "$ref": "#/$defs/Quota"
+}

changedOutput schema / required

Previous value: -[
-  "name",
-  "txid"
-]New value: +[
+  "name",
+  "txid",
+  "quota"
+]

Changed2 schema fields changedJun 15, 2026

changedInput schema / properties / address / description

Previous value: -"Your Emercoin address to bind to your GitHub identity (the anchor for signature login)."New value: +"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)."

changedInput schema / properties / metadata / description

Previous value: -"Optional free-form JSON metadata to store with the identity record."New value: +"Optional JSON object stored verbatim in the identity record, e.g. {\"agent\": \"my-bot\", \"url\": \"https://...\"}. Omit if unused."

First observedJun 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=true), the description discloses critical behaviors: it writes one NVS transaction paid by the gateway, the record reads as `pending` then `confirmed` after ~8 minutes, it is idempotent with metadata replaced rather than merged, metadata is stored verbatim and publicly and cannot be deleted, and the address is not parsed/checked here. No contradiction with annotations; it adds substantial operational context.

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 lengthy but well-organized into two logical paragraphs: first the core purpose and immediate effects, then the limits and edge cases. Every sentence adds useful information, so it earns its length. It is slightly verbose but not redundant, so a 4 is appropriate rather than 5.

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?

The tool is a complex write operation with external chain effects, yet the description covers prerequisites (signed-in session), immediate effects (pending/confirmed), idempotency, size/fee limits, privacy implications, and return values (record name and transaction id). With an output schema present, the return is also clarified. Nothing an agent needs to call it correctly is missing.

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?

Although schema description coverage is 100%, the description adds vital semantics: metadata must stay under 20 KiB or the chain rejects it, every 128 bytes adds ~0.0001 EMC to the gateway fee, and `address` is not validated because control is proven later via a signing challenge. These constraints are not in the schema and materially affect how an agent should call the tool.

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 opens with a specific verb-resource pair: 'Create or rotate your on-chain identity record ai:gh:<github_id>'. It clearly distinguishes the tool from siblings like store_memory and whoami by stating its core function (binding an Emercoin address to a GitHub identity). The purpose is unambiguous and immediately differentiates it from the other tools in the set.

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?

The description explicitly instructs the agent to run `whoami` first to confirm sign-in, and to use `store_memory` afterwards to anchor memories. It also notes that the operation counts against FREE-tier write limits and references `whoami` for those limits. This gives clear when-to-use and when-not-to-use guidance, and points to the correct preceding and succeeding tools.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?