Lovie Company Formation

Get Vendor Bill

vendor_bill_get_vendor_bill

Read-only

Returns one bill the company owes a vendor, by id: amount, vendor, due date and whether it has been paid. Read-only. This is money out; an invoice is money in.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	UUID value wrapper.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`vendorBill`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

addedOutput schema / properties / vendorBill / anyOf

Added value: +[
+  {
+    "properties": {
+      "amountCents": {
+        "type": "string"
+      },
+      "billNumber": {
+        "type": "string"
+      },
+      "cancelledAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "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"
+          }
+        ]
+      },
+      "currencyCode": {
+        "type": "string"
+      },
+      "dueDate": {
+        "type": "string"
+      },
+      "id": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "issueDate": {
+        "type": "string"
+      },
+      "notes": {
+        "anyOf": [
+          {
+            "description": "Free-form description (max 5000 chars).",
+            "properties": {
+              "value": {
+                "maxLength": 5000,
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "paidAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "status": {
+        "enum": [
+          "VENDOR_BILL_STATUS_UNSPECIFIED",
+          "VENDOR_BILL_STATUS_OPEN",
+          "VENDOR_BILL_STATUS_PAID",
+          "VENDOR_BILL_STATUS_CANCELLED"
+        ],
+        "type": "string"
+      },
+      "updatedAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "vendorName": {
+        "anyOf": [
+          {
+            "description": "Human-readable name (1-255 Unicode chars).",
+            "properties": {
+              "value": {
+                "maxLength": 255,
+                "minLength": 1,
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "companyId",
+      "vendorName"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / vendorBill / properties

Removed value: -{
-  "amountCents": {
-    "type": "string"
-  },
-  "billNumber": {
-    "type": "string"
-  },
-  "cancelledAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "companyId": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "createdAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "currencyCode": {
-    "type": "string"
-  },
-  "dueDate": {
-    "type": "string"
-  },
-  "id": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "issueDate": {
-    "type": "string"
-  },
-  "notes": {
-    "description": "Free-form description (max 5000 chars).",
-    "properties": {
-      "value": {
-        "maxLength": 5000,
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "paidAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "status": {
-    "enum": [
-      "VENDOR_BILL_STATUS_UNSPECIFIED",
-      "VENDOR_BILL_STATUS_OPEN",
-      "VENDOR_BILL_STATUS_PAID",
-      "VENDOR_BILL_STATUS_CANCELLED"
-    ],
-    "type": "string"
-  },
-  "updatedAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "vendorName": {
-    "description": "Human-readable name (1-255 Unicode chars).",
-    "properties": {
-      "value": {
-        "maxLength": 255,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-}

removedOutput schema / properties / vendorBill / required
```
Removed value: -[
-  "companyId",
-  "vendorName"
-]
```
removedOutput schema / properties / vendorBill / type
```
Removed value: -"object"
```

First observedAug 11, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the safety profile is well covered. The description adds the single-record-by-id behavior and explains the money-direction semantics, but it does not disclose failure behavior, authentication needs, or other operational details. There is no contradiction with the annotations.

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 two sentences with every clause earning its place: the operation, key fields, read-only status, and the invoice distinction are all included. There is no filler, redundancy, or unnecessary detail.

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

Completeness5/5

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

For a single-parameter, read-only tool with an output schema and readOnlyHint annotation, the description covers what is returned, how it is selected (by id), and the safety profile. No critical invocation detail 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 coverage is 100%: the only parameter, 'id', is documented as a UUID value wrapper. The description only repeats 'by id' and adds no extra syntax or wrapper details, so it sits at the baseline for fully schema-documented parameters.

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?

The description states a specific verb ('Returns'), a clear resource ('one bill the company owes a vendor'), and the selection mechanism ('by id'). It also enumerates the returned fields: amount, vendor, due date, and payment status. The read-only marker and the invoice-vs-vendor-bill distinction further separate this tool from sibling mutation and invoice tools.

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?

The description clearly implies when to use this tool: to fetch a single vendor bill by id, and it is read-only. The 'money out; an invoice is money in' sentence explicitly orients selection toward vendor bills rather than invoices. However, it does not name the sibling list tool as the alternative when retrieving multiple bills, leaving that implicit.

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.