Skip to main content
Glama
Sign In

Lightbringer

by com.lightbringer
OverviewDiscussionsAdmin

List reviews in Lightbringer

list_reviews
Read-only

Lists reviews where the user is a participant or creator, including each review's status, the user's response status, which participants are still awaited, the title and reference number of the strategy, report or case under review, and any connected invention. Strategy reviews are identified separately from report reviews.

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by review status

Output Schema

NameRequiredDescriptionDefault
reviewsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / reviews / items / properties / target / enum
      Previous value: -[
-  "document",
-  "report"
-]New value: +[
+  "document",
+  "report",
+  "strategy"
+]
  2. Changed14 schema fields changed
    • removedOutput schema / properties / reviews / items / properties / agentDocId / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / reviews / items / properties / agentDocId / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / reviews / items / properties / awaiting / items / properties / name / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / reviews / items / properties / awaiting / items / properties / name / type
      Added value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / reviews / items / properties / caseDocument / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "documentId": {
-        "type": "string"
-      },
-      "refNum": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "title": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "documentId"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "documentId": {
+        "type": "string"
+      },
+      "refNum": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "title": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "documentId"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / reviews / items / properties / closedAt / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / reviews / items / properties / closedAt / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / reviews / items / properties / documentId / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / reviews / items / properties / documentId / type
      Added value: +[
+  "string",
+  "null"
+]
    • addedOutput schema / properties / reviews / items / properties / instructions
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • removedOutput schema / properties / reviews / items / properties / myStatus / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / reviews / items / properties / myStatus / type
      Added value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / reviews / items / properties / subject / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "refNum": {
-        "type": "string"
-      },
-      "title": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "refNum"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "refNum": {
+        "type": "string"
+      },
+      "title": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "refNum"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedOutput schema / properties / reviews / items / properties / url
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish read-only, non-destructive, closed-world behavior. The description adds useful behavioral detail about result scope, included fields, and the separation of strategy reviews from report reviews, though it does not mention pagination or auth requirements.

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?

The description is two front-loaded sentences with no filler. The first sentence is dense because it enumerates returned fields, but every clause carries useful information.

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 read-only list tool with one optional parameter, full schema coverage, annotations, and an output schema, the description covers the scope and contents sufficiently. An agent can invoke it correctly without additional descriptive context.

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?

The single optional status parameter is fully documented in the schema with an open/closed enum. The description does not mention the status filter or add meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Lists reviews") and a clear scope: reviews where the user is a participant or creator. It also distinguishes strategy reviews from report reviews, but it does not explicitly differentiate this list operation from the sibling get_review tool.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives such as get_review, nor any when-not conditions. The participant/creator scope implies what results appear, but not when an agent should choose this tool over a single-review fetch.

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

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