Lovie Company Formation

List Companies

company_get_list_companies

Read-only

GetListCompanies retrieves a list of companies with filtering and pagination

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedSep 10, 2026

addedOutput schema / properties / companies / items / properties / address

Added value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "city": {
+          "type": "string"
+        },
+        "country": {
+          "type": "string"
+        },
+        "county": {
+          "type": "string"
+        },
+        "state": {
+          "type": "string"
+        },
+        "street1": {
+          "type": "string"
+        },
+        "street2": {
+          "type": "string"
+        },
+        "zipCode": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / companies / items / properties / aliases

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

addedOutput schema / properties / companies / items / properties / createdAt / anyOf

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

removedOutput schema / properties / companies / items / properties / createdAt / format
```
Removed value: -"date-time"
```
removedOutput schema / properties / companies / items / properties / createdAt / type
```
Removed value: -"string"
```
addedOutput schema / properties / companies / items / properties / ein
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / companies / items / properties / formedOn
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / companies / items / properties / id / anyOf

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

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

removedOutput schema / properties / companies / items / properties / id / properties

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

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

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

removedOutput schema / properties / companies / items / properties / name / properties

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

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

addedOutput schema / properties / companies / items / properties / source

Added value: +{
+  "enum": [
+    "COMPANY_SOURCE_UNSPECIFIED",
+    "COMPANY_SOURCE_LOVIE_FORMATION",
+    "COMPANY_SOURCE_USER_CREATED",
+    "COMPANY_SOURCE_IMPORTED"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / companies / items / properties / stateOfFormation
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / companies / items / properties / updatedAt / anyOf

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

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

addedOutput schema / properties / companies / items / properties / userId / anyOf

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

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

First observedAug 11, 2026

TDQS

C2.9/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 clear. The description adds that the operation supports filtering and pagination, but does not disclose further behavioral details such as default page size, filter combination semantics, or response shape beyond what annotations and 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.

Conciseness4/5

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

The description is a single concise sentence that is easy to parse and front-loads the main action. It slightly wastes words by starting with 'GetListCompanies' instead of the action, but overall it is appropriately sized.

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?

Given the nested filter object, pagination parameters, and multiple similar sibling tools, the description is too thin to fully support correct invocation. It does not explain filter behavior, parameter relationships, or which scenarios this list tool is meant for, despite an output schema being present.

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 carries the burden of explaining parameters. It only says 'filtering and pagination' generically and does not explain the filter object's semantics, how filters combine, or the meaning of pageSize/pageToken. The schema's repeated 'UUID value wrapper' descriptions are also unhelpful.

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 verb ('retrieves') and resource ('a list of companies'), and adds filtering and pagination as key capabilities. However, it does not explicitly distinguish this from sibling tools like company_get_my_companies or company_get_company, which perform similar-looking read operations.

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 about when to use this tool versus alternatives such as company_get_my_companies, company_get_company, or company_get_list_company_members. The intended selection criteria must be inferred from the name and context rather than from the description.

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.