Hopi

Bill splitter

hopi_bill_splitter

Read-onlyIdempotent

Split a restaurant bill between people. In 'itemised' mode, list each item with its amount and who shared it, then add an optional tip and service charge (both percentages applied to each person's own share). In 'even' mode, split one total evenly with an optional tip. Amounts in GBP. Source: https://hopi.co.uk/bill-splitter/

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes	'itemised' splits by item and who had it; 'even' splits one total equally
`items`	No	Itemised mode: each item with its amount and the names who shared it. An item with no names is shared by everyone.
`total`	No	Even mode: the bill total before tip
`people`	No	Itemised mode: names of the people sharing the bill
`tipPercent`	No	Tip as a percentage (default 0)
`peopleCount`	No	Even mode: number of people to split between
`servicePercent`	No	Itemised mode: service charge as a percentage (default 0)

Output Schema

TableJSON Schema

Name	Required	Description
`tip`	No
`mode`	Yes
`total`	No
`summary`	Yes
`perPerson`	Yes
`grandTotal`	Yes
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)
`tipPercent`	Yes
`peopleCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 20, 2026

changedOutput schema / properties / perPerson / type

Previous value: -"number"New value: +[
+  "number",
+  "object"
+]

addedOutput schema / required

Added value: +[
+  "grandTotal",
+  "mode",
+  "perPerson",
+  "source_url",
+  "summary",
+  "tipPercent"
+]

First observedSep 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Discloses non-obvious behavior: tip and service percentages are applied to each person's own share, amounts are in GBP, and service charge only appears in itemised mode. Annotations already convey read-only and idempotent behavior, so the description adds useful context beyond them.

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 concise sentences with the core purpose front-loaded and the source URL at the end. No filler or redundancy; 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?

For a two-mode tool with conditional parameter requirements, the description covers both modes, optional tip/service, currency, and source. The output schema exists to describe return values, so their omission here is not a gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning by clarifying that percentages apply per-person and that amounts are in GBP, which supplements the schema without repeating it.

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 ('Split'), resource ('restaurant bill'), and clearly explains the two modes ('itemised' and 'even'). It is easy to distinguish this tool from generic tip or VAT calculators based on the description alone.

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?

Provides clear context for when to use itemised mode versus even mode, including what each mode requires. It does not explicitly name sibling alternatives or state when not to use this tool, but the internal mode guidance is strong.

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

All Hopi 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?