Emer Ai Tools

This connector has been deprecated

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

Who am I

whoami

Read-onlyIdempotent

Report the current session's identity. Read-only, no sign-in required: an anonymous session gets {authenticated: false} with a hint (not an error), a signed-in one gets {authenticated: true} plus the GitHub-rooted id, login and tariff. Call it to confirm who you are before register_identity / store_memory; an anonymous caller must sign in (GitHub OAuth) first.

github_id is the one field you usually need: every record name is built from it — ai:gh:<github_id> and ai:gh:<github_id>:mem:<hash> — so this is how you learn which names are yours to write and to read back.

tariff is free for every account today; it governs the write limits, currently 10 writes per minute and 100 per trailing 24 hours per account, and writing needs a GitHub account at least 30 days old. quota says how many writes are left right now (and, for a young account, the date writes open); every write returns the same figures, so plan batches with them. Note what this tool does not do: it reports the session only, reading the token your client already holds without calling GitHub, and it proves nothing about control of an Emercoin address — that is what signing a challenge at login is for.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`hint`	No
`quota`	No
`tariff`	No
`github_id`	No
`github_login`	No
`authenticated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 24, 2026
- addedOutput schema / description
```
Added value: +"The current session's identity. `authenticated` is always present; the\nGitHub-rooted fields are present only when signed in, and `hint` only when not."
```
- removedOutput schema / properties / authenticated / default
```
Removed value: -null
```
- removedOutput schema / properties / github_id / default
```
Removed value: -null
```
- removedOutput schema / properties / github_login / default
```
Removed value: -null
```
- removedOutput schema / properties / hint / default
```
Removed value: -null
```
- removedOutput schema / properties / quota / default
```
Removed value: -null
```
- removedOutput schema / properties / tariff / default
```
Removed value: -null
```

Changed2 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: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/Quota"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed13 schema fields changedJun 15, 2026

addedOutput schema / properties / authenticated

Added value: +{
+  "default": null,
+  "title": "Authenticated",
+  "type": "boolean"
+}

addedOutput schema / properties / github_id / anyOf

Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / github_id / default
```
Added value: +null
```
removedOutput schema / properties / github_id / type
```
Removed value: -"integer"
```

addedOutput schema / properties / github_login / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / github_login / default
```
Added value: +null
```
removedOutput schema / properties / github_login / type
```
Removed value: -"string"
```

addedOutput schema / properties / hint

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Hint"
+}

addedOutput schema / properties / tariff / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / tariff / default
```
Added value: +null
```
removedOutput schema / properties / tariff / type
```
Removed value: -"string"
```

removedOutput schema / required

Removed value: -[
-  "github_id",
-  "github_login",
-  "tariff"
-]

changedOutput schema / title

Previous value: -"Identity"New value: +"WhoAmI"

First observedJun 15, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world, but the description adds genuinely new behavioral context: no sign-in required, an anonymous call returns {authenticated: false} with a hint rather than an error, and it reads the client's existing token without contacting GitHub. It also discloses write limits (10/min, 100/24h), the 30-day GitHub account-age requirement, and how quota is reported. Those are real additions, though the tariff/quota discussion is closer to sibling-tool (write) behavior than to identity reporting.

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 and behavior are front-loaded in the first two sentences, and the record-naming rule for github_id comes right after. It is long for a zero-argument tool, and the tariff/quota paragraph is the least essential part and could be compressed or moved to the write tools, but no sentence is pure filler.

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 no-parameter identity probe, the description covers the anonymous and authenticated response shapes, the meaning of the key fields, prerequisites, and the limits that constrain subsequent writes. An output schema exists, yet the explanation of github_id's role in naming records still adds usable context rather than duplicating schema text.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing to disambiguate. The description instead spends its space on field meanings of the response (github_id as the basis of record names, tariff, quota), which is extra value rather than missing parameter information.

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 opening sentence states a specific verb and resource: report the current session's identity. It also implicitly separates itself from siblings by framing the result as the input you need before register_identity or store_memory, so an agent knows this is the identity-probe tool rather than a record or node tool.

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?

It gives an explicit trigger ('Call it to confirm who you are before register_identity / store_memory') and the prerequisite that an anonymous caller must complete GitHub OAuth sign-in first. It also states the exclusion — it does not prove control of an Emercoin address, which is what a login challenge signature does — so the agent knows which tool answers which question.

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?