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

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

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

addedOutput schema / description

Added value: +"The on-chain write: the NVS name written, its transaction id, and the\nwrites this account has left afterwards."

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.7/5.0

Behavior4/5

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

Goes well beyond the annotations: gateway-paid NVS transaction (no EMC needed), `pending` immediately then `confirmed` after ~8 minutes, idempotent rebinding with `metadata` replaced rather than merged, 20 KiB chain limit, per-128-byte fee scaling, and permanent public immutability. Minor gap: it does not say what happens to a previously bound address's prior record beyond 'rebinds', though the replacement semantics are clear.

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?

Purpose is front-loaded in the first sentence and each paragraph covers a distinct concern (prerequisites, chain economics, limits). Slightly over-long, with mild redundancy — 'stored verbatim' and the public-chain immutability warning are restated in the second paragraph, and the address-validation caveat also appears in the schema.

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?

For a two-parameter write tool with an output schema, the description covers everything an agent needs: auth prerequisite, cost/limits, timing of confirmation, idempotency, replacement semantics, and irreversibility. Return values are documented in the output schema, and the description still names what comes back (record name and tx id).

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 already 100%, yet the description still adds value: `address` is deliberately not parsed or validated so typos surface only at login, and `metadata` is stored verbatim, replaced not merged, subject to a 20 KiB cap, and publicly immutable. These are semantics the schema fields do not convey.

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 first sentence names a specific verb and resource ('Create or rotate your on-chain identity record `ai:gh:<github_id>`') and states the binding operation precisely, including the record naming convention. It also routes memory storage to `store_memory` and session checks to `whoami`, so an agent can distinguish it from siblings without opening a schema.

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 prerequisites are given ('Requires a signed-in session (OAuth)', 'Run `whoami` first to confirm you are signed in'), along with the consequence ('counts against the FREE-tier write limits'), the follow-up action ('anchor memories under this identity afterwards with `store_memory`'), and the repeat-call behavior ('calling again rebinds the address'). Very little is left to inference.

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?