Lovie Company Formation

List Field Options

field_get_list_field_options

Read-only

List field options with filtering and pagination

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed37 schema fields changedSep 10, 2026

addedOutput schema / properties / options / 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 / options / items / properties / code / description
```
Removed value: -"Lowercase kebab-case code identifier."
```

removedOutput schema / properties / options / items / properties / code / properties

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

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

addedOutput schema / properties / options / items / properties / companyId / anyOf

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

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

addedOutput schema / properties / options / items / properties / createdAt / anyOf

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

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

addedOutput schema / properties / options / items / properties / description / anyOf

Added value: +[
+  {
+    "description": "Free-form description (max 5000 chars).",
+    "properties": {
+      "value": {
+        "maxLength": 5000,
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / options / items / properties / description / description
```
Removed value: -"Free-form description (max 5000 chars)."
```
removedOutput schema / properties / options / items / properties / description / properties
```
Removed value: -{
-  "value": {
-    "maxLength": 5000,
-    "type": "string"
-  }
-}
```
removedOutput schema / properties / options / items / properties / description / type
```
Removed value: -"object"
```

addedOutput schema / properties / options / items / properties / fieldId / anyOf

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

removedOutput schema / properties / options / items / properties / fieldId / description
```
Removed value: -"UUID value wrapper."
```

removedOutput schema / properties / options / items / properties / fieldId / properties

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

removedOutput schema / properties / options / items / properties / fieldId / type
```
Removed value: -"object"
```

addedOutput schema / properties / options / items / properties / id / anyOf

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

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

removedOutput schema / properties / options / items / properties / id / properties

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

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

addedOutput schema / properties / options / items / properties / metadata / anyOf

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

removedOutput schema / properties / options / items / properties / metadata / properties

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

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

addedOutput schema / properties / options / 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 / options / items / properties / name / description
```
Removed value: -"Human-readable name (1-255 Unicode chars)."
```

removedOutput schema / properties / options / items / properties / name / properties

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

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

addedOutput schema / properties / options / items / properties / parentId / anyOf

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

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

addedOutput schema / properties / options / items / properties / updatedAt / anyOf

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

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

First observedAug 11, 2026

TDQS

B3.2/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, so the safety profile is covered. The description adds useful behavioral context about filtering and pagination, but does not disclose limits, ordering, or other operational traits.

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 front-loaded sentence with no filler. Every word contributes to identifying the action, resource, and key capabilities.

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

Completeness2/5

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

The tool has a nested filter schema, multiple filter criteria, pagination parameters, and several closely related sibling tools. The description is too minimal to orient an agent on field option semantics, required filter structure, or how this differs from suggestion/singular retrieval tools, despite the output schema existing.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it only mentions 'filtering and pagination' generically. It does not explain the required fieldId, the filter's nested properties (ids, parentId, companyId, rootsOnly, includePlatform), or the purpose of pageSize/pageToken.

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 a specific verb and resource: 'List field options' with filtering and pagination. It distinguishes itself from singular getter field_get_field_option by the 'List' action, though it does not explicitly name that sibling.

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 description implies usage when a paginated, filterable list of field options is needed. However, it provides no explicit guidance about when to choose this over field_get_field_option or field_suggest_field_options, leaving the routing decision mostly to inference.

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.