Skip to main content
Glama

Lightbringer

by com.lightbringer
OverviewDiscussionsAdmin

List reviews

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

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by review status

Output Schema

TableJSON 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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: results are permission-scoped to reviews the user participates in or created, and strategy reviews are surfaced separately from report reviews — a meaningful behavioral distinction not visible in the schema.

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?

A single front-loaded sentence that opens with the verb and scope before enumerating fields. It is long, and the field enumeration partially duplicates the output schema, but nothing is padding or tautological.

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?

For a zero-required-parameter list tool with an output schema, the description covers scope, the participant/creator permission boundary, and the strategy-vs-report split. The listed return fields are somewhat redundant given the output schema, but no agent-critical information is missing.

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?

There is only one parameter (status, enum open/closed) and schema coverage is 100%, so the schema fully documents it. The description never mentions filtering by status at all, adding nothing on top of the structured field — baseline 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?

States a specific verb and resource ('Lists reviews') and adds a meaningful scope constraint — only reviews where the user is a participant or creator. That scoping distinguishes it in spirit from the singular get_review sibling, but the description never names that sibling or otherwise explicitly separates the two.

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 by the tool name and the participant/creator scoping, but there is no explicit when-to-use or when-not-to-use statement, and no pointer to get_review for single-record retrieval. An agent must infer the boundary from the sibling list.

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