Lovie Company Formation

List Datatables

datatable_get_list_datatables

Read-only

List datatables (platform + a company's own).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filter`	No
`pageSize`	No
`pageToken`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`datatables`	No
`totalCount`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedSep 10, 2026

addedOutput schema / properties / datatables / items / properties / code / anyOf

Added value: +[
+  {
+    "description": "Lowercase kebab-case code identifier.",
+    "properties": {
+      "value": {
+        "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / datatables / items / properties / code / description
```
Removed value: -"Lowercase kebab-case code identifier."
```

removedOutput schema / properties / datatables / items / properties / code / properties

Removed value: -{
-  "value": {
-    "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
-    "type": "string"
-  }
-}

removedOutput schema / properties / datatables / items / properties / code / type
```
Removed value: -"object"
```

addedOutput schema / properties / datatables / items / properties / companyId / anyOf

Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / datatables / items / properties / companyId / description
```
Removed value: -"UUID value wrapper."
```
removedOutput schema / properties / datatables / items / properties / companyId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
removedOutput schema / properties / datatables / items / properties / companyId / type
```
Removed value: -"object"
```

addedOutput schema / properties / datatables / items / properties / createdAt / anyOf

Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / datatables / items / properties / createdAt / format
```
Removed value: -"date-time"
```
removedOutput schema / properties / datatables / items / properties / createdAt / type
```
Removed value: -"string"
```

addedOutput schema / properties / datatables / items / properties / id / anyOf

Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / datatables / items / properties / id / description
```
Removed value: -"UUID value wrapper."
```

removedOutput schema / properties / datatables / items / properties / id / properties

Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}

removedOutput schema / properties / datatables / items / properties / id / type
```
Removed value: -"object"
```

addedOutput schema / properties / datatables / items / properties / metadata / anyOf

Added value: +[
+  {
+    "properties": {
+      "values": {
+        "additionalProperties": {
+          "type": "string"
+        },
+        "type": "object"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / datatables / items / properties / metadata / properties

Removed value: -{
-  "values": {
-    "additionalProperties": {
-      "type": "string"
-    },
-    "type": "object"
-  }
-}

removedOutput schema / properties / datatables / items / properties / metadata / type
```
Removed value: -"object"
```

addedOutput schema / properties / datatables / items / properties / name / anyOf

Added value: +[
+  {
+    "description": "Human-readable name (1-255 Unicode chars).",
+    "properties": {
+      "value": {
+        "maxLength": 255,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / datatables / items / properties / name / description
```
Removed value: -"Human-readable name (1-255 Unicode chars)."
```

removedOutput schema / properties / datatables / items / properties / name / properties

Removed value: -{
-  "value": {
-    "maxLength": 255,
-    "minLength": 1,
-    "type": "string"
-  }
-}

removedOutput schema / properties / datatables / items / properties / name / type
```
Removed value: -"object"
```

addedOutput schema / properties / datatables / items / properties / updatedAt / anyOf

Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / datatables / items / properties / updatedAt / format
```
Removed value: -"date-time"
```
removedOutput schema / properties / datatables / items / properties / updatedAt / type
```
Removed value: -"string"
```

First observedAug 11, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds only a scope note (platform + company's own) but does not disclose any behavioral aspects like pagination behavior, result size, or side effects. It does not contradict annotations, but it adds minimal behavioral context beyond what annotations provide.

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 a single short sentence, front-loaded with the action and scope. It is concise and avoids wasted words. However, it is so terse that it sacrifices necessary detail, but for conciseness alone, it earns a high score.

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

Completeness1/5

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

Given the tool has three optional parameters, an output schema, and no parameter descriptions anywhere, the description is far from complete. An agent cannot determine what 'filter' means, how pagination works, or what fields are available without additional information. The output schema might help with return values, but input semantics are entirely unaddressed.

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

Parameters1/5

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

Schema description coverage is 0%, meaning the schema provides no descriptions for the three parameters (filter, pageSize, pageToken). The description does not mention or explain any of these parameters, leaving the agent without any semantic understanding of how to construct a valid request. The description entirely fails to compensate for the schema's lack of documentation.

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 clearly states the action (list) and resource (datatables), and adds a scoping detail ('platform + a company's own') that clarifies what is being listed. It is distinct from siblings like datatable_get_datatable_fields and datatable_get_related_datatables, though it does not explicitly name them. The title aligns with the description.

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?

No guidance is provided on when to use this tool versus alternatives such as datatable_get_related_datatables or datatable_get_datatable_fields. There is no mention of prerequisites, filters, or when this listing is appropriate. The description only gives the basic action without any contextual usage hints.

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.