Skip to main content
Glama

HelpySelf

by com.helpyself
OverviewDiscussionsAdmin

Tip Calculator

tip_calculator
Read-onlyIdempotent

Work out the tip and split the bill into amounts people can actually pay. A HelpySelf tool (helpyself.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
billYesThe amount on the bill before any tip, in whatever currency you use. Tax it already contains is handled by taxRate.
peopleYesHow many ways to split the total. 1 means no split.
roundToNoRound each person's share up to this step in the bill's currency: 1 for whole units, 0.5 for halves. 0 or omitted keeps the exact share. Always up, never down.
taxRateNoSales tax already included in bill, as a percentage. It is taken off before the tip is worked out, so the tip is on the pre-tax amount. 0 or omitted tips on the whole bill, which is the norm outside the US.
tipPercentYesThe tip as a percentage of the bill, or of the pre-tax amount when taxRate is set: 15 means 15%.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / bill / description
      Added value: +"The amount on the bill before any tip, in whatever currency you use. Tax it already contains is handled by taxRate."
    • addedInput schema / properties / people / description
      Added value: +"How many ways to split the total. 1 means no split."
    • addedInput schema / properties / roundTo / description
      Added value: +"Round each person's share up to this step in the bill's currency: 1 for whole units, 0.5 for halves. 0 or omitted keeps the exact share. Always up, never down."
    • addedInput schema / properties / taxRate / description
      Added value: +"Sales tax already included in bill, as a percentage. It is taken off before the tip is worked out, so the tip is on the pre-tax amount. 0 or omitted tips on the whole bill, which is the norm outside the US."
    • addedInput schema / properties / tipPercent / description
      Added value: +"The tip as a percentage of the bill, or of the pre-tax amount when taxRate is set: 15 means 15%."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description's phrase 'amounts people can actually pay' hints at rounding behavior but does not explicitly disclose the always-up rounding rule or the tax-rate handling; that detail is left to the schema.

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 core description is a single efficient sentence that front-loads the purpose. The appended 'A HelpySelf tool (helpyself.com)' is branding that adds no invocation value, preventing a perfect score.

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

Completeness3/5

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

The schema and annotations carry most of the weight: parameters are fully described and safety is annotated. The description adds the rounding intent but does not mention return values or edge cases, and with no output schema the agent must infer the result format. It is adequate but not rich.

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 the schema fully documents all five parameters. The description adds no parameter-level detail beyond the schema, matching the baseline for high schema coverage.

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 states a specific action ('work out the tip and split the bill') on a clear resource (a bill), which distinguishes it from the many other sibling calculators. It is not a tautology and leaves no ambiguity about what the tool does.

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

Usage Guidelines3/5

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

The purpose itself implies when to use the tool (when calculating a tip and splitting a bill), but there is no explicit guidance about when not to use it or how it compares to alternatives such as percentage_calculator or vat_calculator. The context is implied rather than stated.

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

All HelpySelf toolsInspect
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