Skip to main content
Glama
tresor4k

macalc

calculate_tip

Compute the tip amount and total bill for a shared meal, including per-person split. Provide bill amount, tip percentage, and number of people for accurate calculations.

Instructions

Compute restaurant tip and per-person split. Use for shared meals. Inputs: bill, tip %, people count. Returns tip, total, per-person share. See list_bundles for related 'vie-quotidienne' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
billYesBill amount
tip_pctNoTip percentage
splitNoNumber of people splitting

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior3/5

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

The description states it 'Compute' and 'Returns' values, implying a read-only operation. Without annotations, it provides basic behavioral context, but it does not mention any edge cases, limitations, or side effects. As a simple calculator, this is adequate but not thorough.

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?

The description is two sentences with a concise structure. It front-loads the purpose and provides all essential information without unnecessary words.

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 an output schema, the description covers purpose, inputs, outputs, and related tools. It is sufficiently complete, though it could mention the output schema briefly.

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 each parameter described. The description lists inputs ('bill, tip %, people count') but adds no new meaning beyond the schema. Baseline score of 3 is appropriate.

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 computes restaurant tip and per-person split for shared meals. It distinguishes itself from siblings like 'calculate_tip_split' and 'calculate_tip_worldwide' by specifying the shared meal context and directing to list_bundles for related calculators, but it does not explicitly differentiate from 'calculate_tip_split'.

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 description says 'Use for shared meals' and suggests seeing list_bundles for related calculators. However, it lacks explicit guidance on when not to use this tool or how it differs from alternatives like 'calculate_tip_split'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server