Lightbringer

Who am I

whoami

Read-only

Returns the signed-in Lightbringer user and organisation for this connection. Optionally includes up to 20 fellow organisation members with names, roles and a total count, with read consent. An unavailable member lookup is reported separately from the profile.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`include_members`	No	Includes a bounded member roster with read consent

Output Schema

TableJSON Schema

Name	Required	Description	Default
`user`	Yes
`members`	No
`organisation`	Yes
`members_error`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 6, 2026

addedInput schema / properties / include_members

Added value: +{
+  "description": "Includes a bounded member roster with read consent",
+  "type": "boolean"
+}

addedOutput schema / properties / members

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "members": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "name": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "role"
+        ],
+        "type": "object"
+      },
+      "maxItems": 20,
+      "type": "array"
+    },
+    "totalCount": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "members",
+    "totalCount"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / members_error
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / organisation / properties / country
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / organisation / properties / state
```
Added value: +{
+  "maxLength": 128,
+  "type": "string"
+}
```
addedOutput schema / properties / organisation / properties / website
```
Added value: +{
+  "maxLength": 2048,
+  "type": "string"
+}
```

Changed6 schema fields changedSep 28, 2026
- removedOutput schema / properties / organisation / properties / name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / organisation / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / user / properties / name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / user / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / user / properties / role / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / user / properties / role / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, non-destructive and non-open-world, so the safety profile is covered. The description adds genuinely new behavior: the roster is bounded to 20, requires read consent, and a failed member lookup is reported separately rather than failing the whole call.

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?

Three tight sentences, front-loaded with the core result and then the optional member behavior and failure semantics. Minor redundancy with the schema's 'read consent' phrase, but nothing wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. The description still covers the default (profile only), the optional branch, and the partial-failure case, leaving only the default value of include_members to inference.

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?

Schema coverage is 100%, so the boolean's meaning is already documented (baseline 3). The description adds the concrete bound of 'up to 20' members and the consent condition, which the schema's generic 'bounded member roster' wording does not quantify.

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?

States a specific verb and resource: returns the signed-in user and organisation scoped to this connection. None of the siblings (list_tasks, get_strategy, search, etc.) do this, so an agent can distinguish it at a glance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: it is the identity/profile lookup for the current connection, and members are only available 'with read consent'. There is no explicit when-to-use, when-not-to-use, or named alternative, though the siblings suggest none exists for this purpose.

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

All Lightbringer 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.