Osome

create-customer

Create an invoice customer for a company and return it. Use the returned id as customerId in update-invoice-draft or submit-invoice. Each call creates a new customer, so check list-customers first to reuse an existing one.

Input Schema

Name	Required	Description	Default
`customer`	Yes	Customer to create. Only name and type are required. Omit fields you don't have; the optional text fields and shippingAddress also accept null, and groupEmails must be an array when sent.
`companyId`	Yes	Company ID

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedNov 4, 2026

addedInput schema / properties / customer / description

Added value: +"Customer to create. Only name and type are required. Omit fields you don't have; the optional text fields and shippingAddress also accept null, and groupEmails must be an array when sent."

addedInput schema / properties / customer / properties / addressLine1 / description
```
Added value: +"Address line 1"
```
addedInput schema / properties / customer / properties / addressLine2 / description
```
Added value: +"Address line 2"
```
addedInput schema / properties / customer / properties / city / description
```
Added value: +"City"
```
addedInput schema / properties / customer / properties / country / description
```
Added value: +"Country name (e.g. Singapore) or two-letter code (SG)"
```
addedInput schema / properties / customer / properties / email / description
```
Added value: +"Main email address"
```
addedInput schema / properties / customer / properties / groupEmails / description
```
Added value: +"Additional email addresses for the customer, besides email"
```
addedInput schema / properties / customer / properties / name / description
```
Added value: +"Customer name"
```
addedInput schema / properties / customer / properties / notes / description
```
Added value: +"Notes about the customer"
```
addedInput schema / properties / customer / properties / phone / description
```
Added value: +"Phone number"
```
addedInput schema / properties / customer / properties / postalCode / description
```
Added value: +"Postal code"
```

changedInput schema / properties / customer / properties / shippingAddress / anyOf

Previous value: -[
-  {
-    "properties": {
-      "addressLine1": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "addressLine2": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "city": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "country": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "postalCode": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "state": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "addressLine1": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Address line 1"
+      },
+      "addressLine2": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Address line 2"
+      },
+      "city": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "City"
+      },
+      "country": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Country name (e.g. Singapore) or two-letter code (SG)"
+      },
+      "postalCode": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Postal code"
+      },
+      "state": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "State or region"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / customer / properties / shippingAddress / description
```
Added value: +"Separate shipping address, if any; every field is optional"
```
addedInput schema / properties / customer / properties / state / description
```
Added value: +"State or region"
```
addedInput schema / properties / customer / properties / type / description
```
Added value: +"individual for a person, company for a business"
```

First observedOct 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive write. The description adds that each call creates a new customer (duplicate risk) and that it returns the created customer for use in other tools, providing useful behavioral context beyond 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?

Three sentences with zero waste: purpose and return are front-loaded, followed by usage of the returned id and a duplicate-creation warning. 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?

Given annotations covering safety and a 100% schema, the description adds necessary context about return value, intended downstream use, and duplicate avoidance. Nothing critical is missing for an agent to call the tool correctly.

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 all parameters and nested fields fully documented in the schema. The description does not add parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 (create) and resource (invoice customer) and distinguishes from list-customers by instructing to check it first for reuse. The return value and intended use are also clarified.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (create a new customer) and when not to (check list-customers to reuse an existing one). Names the alternative and the condition that selects it, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Osome 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.

Resources

Need Help?