RoomSplit

Split utilities

split_utilities

Read-onlyIdempotent

Split utility and household bills across housemates, each bill equally, by occupants, or by usage weight, and total what each person owes. Use for recurring shared bills such as electricity, gas or internet. Do NOT use for rent (use split_rent) or to settle who already paid (use settle_up).

Input Schema

Name	Required	Description	Default
`bills`	Yes	Bills to split (names must be unique), e.g. [{"name":"Electricity","amount":120,"split":"by_usage"}]
`people`	Yes	Housemates sharing the bills (names must be unique), e.g. [{"name":"Asha","usage_weight":2},{"name":"Dev","usage_weight":1}]

Output Schema

Name	Required	Description
`note`	Yes	Plain-language explanation of the totals
`bills`	Yes	Each bill with its per-person shares (shares sum to the bill amount)
`totals`	Yes	Total each person owes across all bills
`grand_total`	Yes	Sum of all bill amounts

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 10, 2026

changedInput schema / properties / bills / description

Previous value: -"Bills to split"New value: +"Bills to split (names must be unique), e.g. [{\"name\":\"Electricity\",\"amount\":120,\"split\":\"by_usage\"}]"

addedInput schema / properties / bills / items / properties / amount / description
```
Added value: +"Bill total, positive number, e.g. 120"
```
addedInput schema / properties / bills / items / properties / name / description
```
Added value: +"Unique bill label, e.g. 'Electricity'"
```

addedInput schema / properties / bills / items / properties / split / description

Added value: +"'equal' per person, 'by_occupants' weighted by each person's occupants, or 'by_usage' weighted by usage_weight (required on everyone)"

addedInput schema / properties / bills / minItems
```
Added value: +1
```

changedInput schema / properties / people / description

Previous value: -"People sharing the house"New value: +"Housemates sharing the bills (names must be unique), e.g. [{\"name\":\"Asha\",\"usage_weight\":2},{\"name\":\"Dev\",\"usage_weight\":1}]"

addedInput schema / properties / people / items / properties / name / description
```
Added value: +"Unique housemate name"
```

addedInput schema / properties / people / items / properties / occupants / description

Added value: +"How many people this housemate pays for (by_occupants bills), positive, default 1"

addedInput schema / properties / people / items / properties / usage_weight / description

Added value: +"Relative usage for by_usage bills, positive, e.g. 2 for double use, 0.5 for a light user"

addedInput schema / properties / people / minItems
```
Added value: +1
```

addedOutput schema / properties / bills

Added value: +{
+  "description": "Each bill with its per-person shares (shares sum to the bill amount)",
+  "items": {
+    "properties": {
+      "amount": {
+        "description": "Bill total, rounded to cents",
+        "type": "number"
+      },
+      "name": {
+        "description": "Bill label",
+        "type": "string"
+      },
+      "shares": {
+        "description": "Each person's share of this bill",
+        "items": {
+          "properties": {
+            "amount": {
+              "description": "Amount, rounded to cents",
+              "type": "number"
+            },
+            "name": {
+              "description": "Person's name",
+              "type": "string"
+            }
+          },
+          "required": [
+            "name",
+            "amount"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "split": {
+        "description": "Split rule applied",
+        "enum": [
+          "equal",
+          "by_occupants",
+          "by_usage"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "amount",
+      "split",
+      "shares"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / grand_total

Added value: +{
+  "description": "Sum of all bill amounts",
+  "type": "number"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "Plain-language explanation of the totals",
+  "type": "string"
+}

removedOutput schema / properties / split_results

Removed value: -{
-  "description": "List of split results for each person",
-  "items": {
-    "properties": {
-      "bill_details": {
-        "description": "Details of each bill and the person's share",
-        "items": {
-          "properties": {
-            "amount_owed": {
-              "description": "Amount owed by the person for this bill",
-              "type": "number"
-            },
-            "bill_name": {
-              "description": "Name of the bill",
-              "type": "string"
-            }
-          },
-          "required": [
-            "bill_name",
-            "amount_owed"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "name": {
-        "description": "Name of the person",
-        "type": "string"
-      },
-      "total_owed": {
-        "description": "Total amount owed by the person",
-        "type": "number"
-      }
-    },
-    "required": [
-      "name",
-      "total_owed",
-      "bill_details"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / totals

Added value: +{
+  "description": "Total each person owes across all bills",
+  "items": {
+    "properties": {
+      "amount": {
+        "description": "Amount, rounded to cents",
+        "type": "number"
+      },
+      "name": {
+        "description": "Person's name",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "amount"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "split_results"
-]New value: +[
+  "bills",
+  "totals",
+  "grand_total",
+  "note"
+]

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "split_results": {
+      "description": "List of split results for each person",
+      "items": {
+        "properties": {
+          "bill_details": {
+            "description": "Details of each bill and the person's share",
+            "items": {
+              "properties": {
+                "amount_owed": {
+                  "description": "Amount owed by the person for this bill",
+                  "type": "number"
+                },
+                "bill_name": {
+                  "description": "Name of the bill",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "bill_name",
+                "amount_owed"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "name": {
+            "description": "Name of the person",
+            "type": "string"
+          },
+          "total_owed": {
+            "description": "Total amount owed by the person",
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "total_owed",
+          "bill_details"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "split_results"
+  ],
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), lowering the bar. The description adds real value beyond that by characterizing the operation as a pure calculation that also aggregates ('total what each person owes') and by scoping it to recurring shared bills. It does not disclose rounding, currency handling, or the result shape, but the output schema exists to carry return values.

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, front-loaded with the core purpose, followed by inclusion criteria and then the two exclusions with alternatives. Every sentence earns its place with no filler.

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?

Purpose, routing to siblings, and supported split modes are all covered, and an output schema exists so return-value detail is unnecessary. Nothing an agent needs to select or invoke this tool correctly 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%, so both top-level params and the nested split enum are fully documented in the schema. The description restates the three split modes (equal, by occupants, by usage weight) but adds no syntax, uniqueness, or weighting semantics beyond what the schema already says. Baseline 3 is correct when the schema does the heavy lifting.

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 ('Split utility and household bills across housemates') and names the three supported split modes, so the agent knows exactly what computation this performs. It also explicitly distinguishes itself from split_rent and settle_up, making sibling selection unambiguous.

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?

Gives positive guidance ('Use for recurring shared bills such as electricity, gas or internet') and explicit exclusions with the correct alternative named for each ('Do NOT use for rent (use split_rent)', 'to settle who already paid (use settle_up)'). Nothing is left to inference.

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

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