Lightbringer

Read Lightbringer connection profile

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

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

Output 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

A3.9/5.0

Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, so the bar is lower. The description adds real value beyond them: the member roster is bounded at 20, requires 'read consent', and a failed member lookup is reported separately from the profile rather than failing the whole call. It does not state anything about token scopes or auth failure modes.

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 with the core answer front-loaded and the optional member behavior and its partial-failure semantics following. No filler, though the final clause is dense enough to need a second read.

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 restated, and the single optional parameter is documented in both schema and description. The partial-failure disclosure closes the main ambiguity for an agent acting on the result; only auth/permission expectations are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already carries include_members as a boolean for the bounded roster. The description does add meaning by naming the bound (up to 20) and the returned member fields (names, roles, total count), which is more than the schema conveys, but it stops short of useful mechanics.

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 pair: 'Returns the signed-in Lightbringer user and organisation for this connection.' No sibling tool in the list (get_company_context, list_tasks, etc.) does identity/connection resolution, so an agent can route here unambiguously.

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 only implied by the identity-returning purpose; there is no explicit statement of when to call this versus alternatives such as get_company_context, nor any prerequisite or exclusion. The description does clarify the optional-members branch, which is a partial substitute for call guidance.

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.