macalc

calculate_tip_split

Calculate tip and per-person amount for a restaurant bill. See list_bundles for related 'vie-quotidienne' calculators.

Input Schema

TableJSON Schema

Name	Required	Description
`tip_pct`	Yes	Tip percentage
`num_people`	Yes	Number of people splitting
`bill_amount`	Yes	Total bill amount

Output Schema

TableJSON Schema

Name	Required	Description
`result`	No	Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
`source`	No	Authoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
`formula`	No	Human-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
`reference_url`	No	Link to a calcul2 page documenting the calculation in detail.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedApr 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "formula": {
+      "description": "Human-readable formula or method used (e.g. \"I=P·r·t\", \"Magnus formula\").",
+      "type": "string"
+    },
+    "reference_url": {
+      "description": "Link to a calcul2 page documenting the calculation in detail.",
+      "type": "string"
+    },
+    "result": {
+      "description": "Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools)."
+    },
+    "source": {
+      "description": "Authoritative source for the rule or formula (e.g. \"Article 197 CGI\", \"NF DTU 21\").",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedApr 8, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided; description does not disclose any behavioral traits beyond the obvious calculation, lacking info on precision or side effects.

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?

Two sentences, no fluff, front-loaded with the core purpose and a pointer to related tools.

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?

Sufficient given high schema coverage and output schema exists; could briefly mention typical outputs like tip amount and total per person.

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% with clear parameter descriptions; tool description adds no additional meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it calculates tip and per-person amount for a restaurant bill, but does not differentiate from siblings like 'calculate_tip' or 'calculate_tip_worldwide'.

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

Usage Guidelines2/5

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

Only mentions 'See list_bundles for related calculators' with no explicit guidance on when to use this tool versus alternatives.

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

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