Skip to main content
Glama

TrueCalci

by com.truecalci

tip_splitter

Compute restaurant bill gratuity, total payable bill, and fair per-person itemized payment split across dining parties.

Behavior: Deterministic, idempotent calculation with zero external side effects. Multiplies pre-tip subtotal by tip percentage, computes total bill including tip, and divides by party size to provide per-guest charge with fair penny rounding.

Usage Guidelines: Use for restaurant dining bills, food delivery tips, and group expense splitting. Do not use for commercial corporate tax or VAT; use vat_sales_tax instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numPeopleNoTotal number of guests sharing the bill. Must be an integer greater than or equal to 1.
billAmountYesPre-tip subtotal or total food and beverage bill in monetary units. Must be positive.
tipPercentNoGratuity percentage to add (e.g. 15, 18, 20, 25%).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • changedInput schema / properties / billAmount / description
      Previous value: -"Subtotal or total bill before tip"New value: +"Pre-tip subtotal or total food and beverage bill in monetary units. Must be positive."
    • changedInput schema / properties / numPeople / description
      Previous value: -"Number of guests dining"New value: +"Total number of guests sharing the bill. Must be an integer greater than or equal to 1."
    • changedInput schema / properties / tipPercent / description
      Previous value: -"Tip percentage (e.g. 15, 18, 20, 25)"New value: +"Gratuity percentage to add (e.g. 15, 18, 20, 25%)."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It explicitly states 'Deterministic, idempotent calculation with zero external side effects' and describes the calculation steps including 'fair penny rounding.' The only notable gap is that the return format or error handling is not stated, but for a simple calculator this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized with a front-loaded purpose, a behavior section, and a usage section. It is efficient and every paragraph earns its place. There is slight redundancy between the opening sentence and the behavior paragraph, but no filler or irrelevant detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple calculator with all parameters documented in the schema, the description is nearly complete: it covers use cases, exclusions, computation behavior, and side-effect profile. The only missing piece is an explicit statement of the return object shape, which would be more critical since no output schema is provided.

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 earns an extra point by explaining how billAmount, tipPercent, and numPeople are used in the calculation ('Multiplies pre-tip subtotal by tip percentage... divides by party size') and by adding 'fair penny rounding' semantics that are not present in the schema.

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 opens with a specific verb and resource: 'Compute restaurant bill gratuity, total payable bill, and fair per-person itemized payment split.' This immediately tells an agent what the tool produces and distinguishes it from generic payment or tax tools. It also names vat_sales_tax as a sibling alternative, further clarifying scope.

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?

Provides explicit 'Use for' scenarios (restaurant dining bills, food delivery tips, group expense splitting) and an explicit 'Do not use for' exclusion (commercial corporate tax or VAT) with a named alternative, vat_sales_tax. This gives an agent clear routing guidance without needing to infer.

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

All TrueCalci toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Every tool targets a separate calculation formula or regulatory context, and descriptions include explicit 'do not use... use X instead' cross-references that clearly separate similar calculators. Even overlapping financial/loan/tax tools are disambiguated by geography, employment model, or specific formula.

Naming Consistency4/5

All tool names are lowercase snake_case and follow a domain/acronym-plus-descriptor pattern, making the set visually and structurally consistent. Minor outliers like casio_991_solve and heavy acronyms (npv_irr, scorp_optimizer) prevent it from being perfectly uniform.

Tool Count2/5

At 28 tools, the server is above the 25-tool threshold that makes broad tool scanning costly for an agent. Every calculator is distinct, but the mix of unrelated domains (tax, fluid mechanics, rocket equations, restaurant tips) means most agents will only ever need a small subset.

Completeness4/5

The set covers a wide range of self-contained calculation domains, from finance and tax to physics and everyday bills, with no obvious dead ends—each tool returns a complete result. Missing general-purpose utilities such as unit/currency conversion or descriptive statistics are notable gaps, but they are workaroundable and don't break the server's specialized calculator model.

Resources