Lovie Company Formation

Get Related Datatables

datatable_get_related_datatables

Read-only

Resolve the child datatables related to a parent (for the UI field picker).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`companyId`	No	UUID value wrapper.
`parentDatatableCode`	Yes	Lowercase kebab-case code identifier.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`related`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

addedOutput schema / properties / related / items / properties / child / anyOf

Added value: +[
+  {
+    "properties": {
+      "code": {
+        "anyOf": [
+          {
+            "description": "Lowercase kebab-case code identifier.",
+            "properties": {
+              "value": {
+                "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "companyId": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "createdAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "id": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "metadata": {
+        "anyOf": [
+          {
+            "properties": {
+              "values": {
+                "additionalProperties": {
+                  "type": "string"
+                },
+                "type": "object"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "name": {
+        "anyOf": [
+          {
+            "description": "Human-readable name (1-255 Unicode chars).",
+            "properties": {
+              "value": {
+                "maxLength": 255,
+                "minLength": 1,
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "updatedAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "code",
+      "name"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / related / items / properties / child / properties

Removed value: -{
-  "code": {
-    "description": "Lowercase kebab-case code identifier.",
-    "properties": {
-      "value": {
-        "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "companyId": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "createdAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "id": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "metadata": {
-    "properties": {
-      "values": {
-        "additionalProperties": {
-          "type": "string"
-        },
-        "type": "object"
-      }
-    },
-    "type": "object"
-  },
-  "name": {
-    "description": "Human-readable name (1-255 Unicode chars).",
-    "properties": {
-      "value": {
-        "maxLength": 255,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "updatedAt": {
-    "format": "date-time",
-    "type": "string"
-  }
-}

removedOutput schema / properties / related / items / properties / child / required
```
Removed value: -[
-  "code",
-  "name"
-]
```
removedOutput schema / properties / related / items / properties / child / type
```
Removed value: -"object"
```

First observedAug 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the hierarchical relationship (child-to-parent) but does not disclose behavior such as pagination, ordering, or any side effects beyond what annotations and the output schema already imply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that front-loads the core action and resource ('Resolve the child datatables related to a parent') and adds the UI context at the end. Every word earns its place; there is no filler or redundancy.

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 simple read-only resolver with a nested parameter schema, an output schema, and safety-preserving annotations, the description is largely complete. The only meaningful gap is the lack of usage guidance relative to sibling datatable tools, but nothing essential for invoking the tool correctly 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?

Schema description coverage is 100%, with both parentDatatableCode and companyId already described in the schema. The prose description does not add additional parameter semantics beyond the schema, which meets the baseline for fully covered parameters.

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 uses a specific verb ('Resolve') and resource ('child datatables related to a parent'), which clearly conveys what the tool does. It does not explicitly distinguish itself from sibling datatable tools like datatable_get_list_datatables or datatable_get_datatable_fields, so it falls just short of a 5.

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?

The phrase 'for the UI field picker' provides a clear use case context, implying when this tool is relevant. However, it does not offer explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or conditions that would rule out sibling tools.

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

All Lovie Company Formation 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.