Lovie Company Formation

Get Invoice Settings

invoice_settings_get_invoice_settings

Read-only

Returns a company's invoicing defaults: numbering, payment terms, currency, tax rate and the branding that appears on a rendered invoice. Read-only. Read this before creating an invoice if you need to know what the defaults will be.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`settings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

addedOutput schema / properties / settings / anyOf

Added value: +[
+  {
+    "properties": {
+      "companyAddress": {
+        "type": "string"
+      },
+      "companyEmail": {
+        "type": "string"
+      },
+      "companyId": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "companyName": {
+        "type": "string"
+      },
+      "companyPhone": {
+        "type": "string"
+      },
+      "companyTaxId": {
+        "type": "string"
+      },
+      "createdAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "defaultNotes": {
+        "type": "string"
+      },
+      "defaultPaymentTerms": {
+        "enum": [
+          "PAYMENT_TERMS_UNSPECIFIED",
+          "PAYMENT_TERMS_DUE_ON_RECEIPT",
+          "PAYMENT_TERMS_NET_7",
+          "PAYMENT_TERMS_NET_15",
+          "PAYMENT_TERMS_NET_30",
+          "PAYMENT_TERMS_NET_60",
+          "PAYMENT_TERMS_CUSTOM"
+        ],
+        "type": "string"
+      },
+      "defaultTaxRateBps": {
+        "type": "integer"
+      },
+      "id": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "invoicePrefix": {
+        "type": "string"
+      },
+      "logoUrl": {
+        "type": "string"
+      },
+      "nextInvoiceNumber": {
+        "type": "integer"
+      },
+      "primaryColor": {
+        "type": "string"
+      },
+      "updatedAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "companyId"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / settings / properties

Removed value: -{
-  "companyAddress": {
-    "type": "string"
-  },
-  "companyEmail": {
-    "type": "string"
-  },
-  "companyId": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "companyName": {
-    "type": "string"
-  },
-  "companyPhone": {
-    "type": "string"
-  },
-  "companyTaxId": {
-    "type": "string"
-  },
-  "createdAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "defaultNotes": {
-    "type": "string"
-  },
-  "defaultPaymentTerms": {
-    "enum": [
-      "PAYMENT_TERMS_UNSPECIFIED",
-      "PAYMENT_TERMS_DUE_ON_RECEIPT",
-      "PAYMENT_TERMS_NET_7",
-      "PAYMENT_TERMS_NET_15",
-      "PAYMENT_TERMS_NET_30",
-      "PAYMENT_TERMS_NET_60",
-      "PAYMENT_TERMS_CUSTOM"
-    ],
-    "type": "string"
-  },
-  "defaultTaxRateBps": {
-    "type": "integer"
-  },
-  "id": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "invoicePrefix": {
-    "type": "string"
-  },
-  "logoUrl": {
-    "type": "string"
-  },
-  "nextInvoiceNumber": {
-    "type": "integer"
-  },
-  "primaryColor": {
-    "type": "string"
-  },
-  "updatedAt": {
-    "format": "date-time",
-    "type": "string"
-  }
-}

removedOutput schema / properties / settings / required
```
Removed value: -[
-  "companyId"
-]
```
removedOutput schema / properties / settings / 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 declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that this returns defaults and enumerates them, but it does not disclose behavior such as behavior for unknown company IDs or partial defaults. No contradiction with 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?

Two short sentences carry the core purpose, the return scope, and the usage moment with no filler. The key purpose is front-loaded, and every sentence earns its place.

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?

This is a simple read-only lookup with one required parameter, full schema coverage, an output schema, and annotations covering safety. The description gives the purpose, the relevant time to use it, and the content returned, so nothing essential is missing for correct invocation.

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 description coverage is 100%, with companyId documented as a UUID value wrapper. The description adds no parameter-specific meaning, but since the schema fully covers the only parameter, the baseline score of 3 applies.

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 action ('Returns...') with a clear resource: a company's invoicing defaults. It enumerates exact content (numbering, payment terms, currency, tax rate, branding), which unambiguously distinguishes it from invoice retrieval or listing siblings.

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 gives explicit context: 'Read this before creating an invoice if you need to know what the defaults will be.' This is a clear when-to-use signal. It does not state when not to use it or name alternatives, but no direct sibling settings tool appears in the list, so the gap is minor.

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.