Skip to main content
Glama

Brain Scanner

by io.github.kevin-lozada-santos
OverviewDiscussionsAdmin

validation_write

Idempotent

Access the validation write operations listed below. Compatibility dispatcher; prefer the individually named tool when available. Select operation and its matching payload. Supported operations: validate_node. Effects and required fields depend on that operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payloadYesArguments for the selected operation. Follow its matching oneOf branch; fields and side effects differ by operation.
operationYesExact operation to dispatch; prefer its individually named tool when available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / oneOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "operation": {
-        "const": "validate_node",
-        "type": "string"
-      },
-      "payload": {
-        "additionalProperties": false,
-        "properties": {
-          "details": {
-            "additionalProperties": false,
-            "properties": {
-              "referenceIds": {
-                "items": {
-                  "maxLength": 500,
-                  "minLength": 1,
-                  "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
-                  "type": "string"
-                },
-                "maxItems": 100,
-                "type": "array",
-                "uniqueItems": true
-              },
-              "status": {
-                "maxLength": 200,
-                "minLength": 1,
-                "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
-                "type": "string"
-              },
-              "summary": {
-                "maxLength": 240,
-                "type": "string"
-              }
-            },
-            "type": "object"
-          },
-          "executionId": {
-            "maxLength": 200,
-            "minLength": 1,
-            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
-            "type": "string"
-          },
-          "idempotencyKey": {
-            "maxLength": 128,
-            "minLength": 16,
-            "pattern": "^[A-Za-z0-9_-]+$",
-            "type": "string"
-          },
-          "nodeId": {
-            "maxLength": 500,
-            "minLength": 1,
-            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
-            "type": "string"
-          },
-          "projectId": {
-            "maxLength": 200,
-            "minLength": 1,
-            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
-            "type": "string"
-          },
-          "sessionId": {
-            "maxLength": 200,
-            "minLength": 1,
-            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
-            "type": "string"
-          }
-        },
-        "required": [
-          "projectId",
-          "nodeId",
-          "idempotencyKey"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "operation",
-      "payload"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "operation": {
+        "const": "validate_node",
+        "description": "Select this exact operation; payload must match this branch.",
+        "type": "string"
+      },
+      "payload": {
+        "additionalProperties": false,
+        "properties": {
+          "details": {
+            "additionalProperties": false,
+            "description": "Optional bounded metadata using only the listed fields, such as summary, status and referenceIds. Not arbitrary command arguments or source content.",
+            "properties": {
+              "referenceIds": {
+                "items": {
+                  "description": "Target node ID from this project's published graph; use get_roots and get_graph_scope to discover nodes. Not a file path.",
+                  "maxLength": 500,
+                  "minLength": 1,
+                  "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
+                  "type": "string"
+                },
+                "maxItems": 100,
+                "type": "array",
+                "uniqueItems": true
+              },
+              "status": {
+                "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
+                "maxLength": 200,
+                "minLength": 1,
+                "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
+                "type": "string"
+              },
+              "summary": {
+                "maxLength": 240,
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "executionId": {
+            "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
+            "maxLength": 200,
+            "minLength": 1,
+            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
+            "type": "string"
+          },
+          "idempotencyKey": {
+            "description": "Caller-generated retry key. Reuse the same key and identical payload only to retry the same mutation; use a new key for a new action.",
+            "maxLength": 128,
+            "minLength": 16,
+            "pattern": "^[A-Za-z0-9_-]+$",
+            "type": "string"
+          },
+          "nodeId": {
+            "description": "Target node ID from this project's published graph; use get_roots and get_graph_scope to discover nodes. Not a file path.",
+            "maxLength": 500,
+            "minLength": 1,
+            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
+            "type": "string"
+          },
+          "projectId": {
+            "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
+            "maxLength": 200,
+            "minLength": 1,
+            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
+            "type": "string"
+          },
+          "sessionId": {
+            "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
+            "maxLength": 200,
+            "minLength": 1,
+            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
+            "type": "string"
+          }
+        },
+        "required": [
+          "projectId",
+          "nodeId",
+          "idempotencyKey"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "operation",
+      "payload"
+    ],
+    "type": "object"
+  }
+]
    • addedInput schema / properties / operation / description
      Added value: +"Exact operation to dispatch; prefer its individually named tool when available."
    • addedInput schema / properties / payload / description
      Added value: +"Arguments for the selected operation. Follow its matching oneOf branch; fields and side effects differ by operation."
  2. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With write annotations present, the description should add context, but "Effects and required fields depend on that operation" merely defers to validate_node without disclosing what the write actually does. It does not describe side effects, permission needs, or what a successful validate_node call produces, leaving the behavioral burden entirely on annotations and the sibling.

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 short and front-loads the dispatcher role and the routing preference. The final sentence ("Effects and required fields depend on that operation") is largely filler that restates the oneOf structure, slightly diluting an otherwise tight passage.

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

Completeness3/5

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

For a dispatcher wrapping a single operation with complete schema descriptions, the description is minimally adequate: it identifies the operation and defers to the named sibling. However, an agent gets no information about what validate_node does or when the compatibility path is required, so the picture is incomplete even if the schema fills in argument detail.

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 projectId, nodeId, idempotencyKey and the nested details fields are fully documented in the schema itself. The description only says "Select operation and its matching payload," adding no semantics beyond the structured definition, which matches the baseline for complete schema coverage.

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 states this is a compatibility dispatcher for validation write operations and names the single supported operation, validate_node, so an agent knows the verb+resource. It is slightly indirect ("Access the validation write operations listed below") and its real substance is just one operation, but the dispatcher framing is unambiguous.

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

Usage Guidelines4/5

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

It gives a clear routing rule: "Compatibility dispatcher; prefer the individually named tool when available," which tells the agent to reach for the sibling validate_node first. It stops short of stating the concrete condition under which this dispatcher must be used instead (e.g., legacy clients), so it is strong but not fully explicit.

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

All Brain Scanner toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources