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

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON 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.

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

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds substantial behavioral context beyond that: no sign-in required, anonymous sessions get a hint rather than an error, the tool reads the client-held token without calling GitHub, and it does not prove Emercoin address control. This fully discloses behavior and limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence earns its place: it front-loads the core identity report, then covers usage context, field semantics, write-limit implications, and exclusions. The structure is logical and the length is justified given the tool has no parameters and must explain return semantics and constraints.

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 zero-parameter identity-check tool, the description is complete: it covers output shape, authentication states, usage before related tools, naming conventions, write limits, quota, and what the tool does not prove. An agent has everything needed to call it correctly and interpret its result.

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 has zero parameters, so parameter semantics are inherently minimal; the rubric assigns a baseline of 4 for 0-param tools. The description adds value by explaining the meaning of output fields like github_id, tariff, and quota, which helps the agent interpret the response even though there are no inputs to document.

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 and resource: 'Report the current session's identity.' It clearly distinguishes this tool from siblings by stating what it does not do—it reports the session only輩and by naming related tools like register_identity and store_memory, so an agent can tell them apart.

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 gives explicit when-to-use guidance: 'Call it to confirm who you are before register_identity / store_memory,' and states when not to rely on it—'it proves nothing about control of an Emercoin address.' It also explains the anonymous vs. signed-in paths and the sign-in requirement, leaving no ambiguity about when this tool is appropriate.

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?