Lovie Company Formation

Create Vendor Bill

vendor_bill_create_vendor_bill

Proposes a bill the company owes a vendor. Nothing is recorded yet: a person accepts or rejects the proposal in Lovie before the bill exists or reaches the books, so tell them it is waiting for them. Returns proposal_id, the proposal waiting for them; there is no bill id until a person accepts it. It never pays or moves money.

Input Schema

Name	Required	Description	Default
`vendorBill`	Yes

Output Schema

Name	Required	Description	Default
`proposalId`	No
`vendorBillId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 29, 2026

addedInput schema / properties / vendorBill / properties / counterpartyId

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

addedInput schema / properties / vendorBill / properties / externalRef

Added value: +{
+  "maxLength": 255,
+  "pattern": "^[A-Za-z0-9._@+/=-]*$",
+  "type": "string"
+}

addedInput schema / properties / vendorBill / properties / lineItems

Added value: +{
+  "items": {
+    "properties": {
+      "amountCents": {
+        "type": "integer"
+      },
+      "companyId": {
+        "description": "UUID value wrapper.",
+        "properties": {
+          "value": {
+            "format": "uuid",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "createdAt": {
+        "format": "date-time",
+        "type": "string"
+      },
+      "currencyCode": {
+        "pattern": "^([A-Z]{3})?$",
+        "type": "string"
+      },
+      "description": {
+        "description": "Free-form description (max 5000 chars).",
+        "properties": {
+          "value": {
+            "maxLength": 5000,
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "id": {
+        "description": "UUID value wrapper.",
+        "properties": {
+          "value": {
+            "format": "uuid",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "lineIndex": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "quantity": {
+        "pattern": "^(-?[0-9]+\\.[0-9]{1,4})?$",
+        "type": "string"
+      },
+      "serviceName": {
+        "maxLength": 200,
+        "type": "string"
+      },
+      "servicePeriodEnd": {
+        "pattern": "^([0-9]{4}-[0-9]{2}-[0-9]{2})?$",
+        "type": "string"
+      },
+      "servicePeriodStart": {
+        "pattern": "^([0-9]{4}-[0-9]{2}-[0-9]{2})?$",
+        "type": "string"
+      },
+      "updatedAt": {
+        "format": "date-time",
+        "type": "string"
+      },
+      "vendorBillId": {
+        "description": "UUID value wrapper.",
+        "properties": {
+          "value": {
+            "format": "uuid",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      }
+    },
+    "type": "object"
+  },
+  "maxItems": 500,
+  "type": "array"
+}

addedInput schema / properties / vendorBill / properties / servicePeriodEnd

Added value: +{
+  "pattern": "^([0-9]{4}-[0-9]{2}-[0-9]{2})?$",
+  "type": "string"
+}

addedInput schema / properties / vendorBill / properties / servicePeriodStart

Added value: +{
+  "pattern": "^([0-9]{4}-[0-9]{2}-[0-9]{2})?$",
+  "type": "string"
+}

addedInput schema / properties / vendorBill / properties / source

Added value: +{
+  "enum": [
+    "VENDOR_BILL_SOURCE_UNSPECIFIED",
+    "VENDOR_BILL_SOURCE_MANUAL",
+    "VENDOR_BILL_SOURCE_GMAIL"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedOct 8, 2026

addedOutput schema / properties / proposalId

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

removedOutput schema / required
```
Removed value: -[
-  "vendorBillId"
-]
```

Changed4 schema fields changedSep 10, 2026

addedOutput schema / properties / vendorBillId / anyOf

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

removedOutput schema / properties / vendorBillId / description
```
Removed value: -"UUID value wrapper."
```

removedOutput schema / properties / vendorBillId / properties

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

removedOutput schema / properties / vendorBillId / type
```
Removed value: -"object"
```

First observedAug 11, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: nothing is recorded, a human gate exists in Lovie before the bill reaches the books, there is no bill id until acceptance, and the tool never pays or moves money. This is exactly the kind of side-effect and lifecycle disclosure an agent needs for a mutation-like tool.

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?

Four short sentences, front-loaded with the nature of the action and the crucial 'nothing is recorded yet' caveat before the return-value detail. No filler.

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?

Given an output schema exists, the description needn't explain returns, yet it helpfully clarifies proposal_id semantics. The main remaining gap is the unaddressed nested input object, but the core behavioral picture is complete.

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% and the single parameter is a deeply nested vendorBill object with many fields (companyId, vendorName, amountCents, lineItems, dates, enums). The description says nothing about which fields to supply or how to format them, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Proposes a bill the company owes a vendor') and immediately distinguishes the action from real creation ('Nothing is recorded yet'), which separates it from sibling write tools like vendor_bill_mark_vendor_bill_paid or vendor_bill_cancel_vendor_bill.

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 clearly frames the workflow: a person must accept or reject the proposal, and the agent should tell them it is waiting. There is no explicit statement of when NOT to use it or a named alternative, but the human-in-the-loop condition is a strong usage cue.

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.