xupersplit

Create a split

create_split

Create a new xupersplit for sharing expenses in a group. No account needed. Returns a secret link — give it to the user and tell them to share it with the group, since anyone holding the link can see and edit the split.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "participants": "<participants>"
    },
    "name": "create_split"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	What the split is for, e.g. "Ski trip".
`currency`	No	Currency code. Defaults to SEK.
`participants`	Yes	Names of everyone splitting, at least two.

Output Schema

Name	Required	Description	Default
`key`	Yes
`url`	Yes
`title`	Yes
`secure`	Yes
`entries`	Yes
`settled`	Yes
`currency`	Yes
`created_at`	Yes
`settlement`	Yes
`total_spent`	Yes
`participants`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 2, 2026
- removedOutput schema / properties / entries / items / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / entries / items / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / entries / items / properties / to / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / entries / items / properties / to / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedAug 3, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes well beyond them by disclosing that no account is required, that the tool returns a secret link, and — critically — that anyone holding the link can see AND edit the split. That access-model disclosure is exactly the kind of behavioral trait an agent needs before creating and distributing a credential.

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 short sentences, front-loaded with the purpose and then the highest-risk fact (the secret link and its edit access). Nothing is redundant or padded.

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?

Although an output schema exists, the description still surfaces the single most important aspect of the return value — that it is a secret, editable-by-anyone link the agent must relay to the user. Combined with the full schema coverage and annotations, an agent has everything needed to call this 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%, so title, currency and participants are already documented in the schema, including the currency enum and default. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the work.

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 ("Create a new xupersplit for sharing expenses in a group") and implicitly scopes it against siblings like get_split, add_expense and add_participant by making clear this is the creation step for a whole split. An agent can distinguish it from every sibling without opening a schema.

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?

"No account needed" and the directive to hand the secret link to the user and tell them to share it give clear operational context for when and how to use the tool. It stops short of explicit exclusions or naming alternatives (e.g. use add_expense afterwards, use get_split to re-read), so it is clear context without full routing guidance.

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

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