Skip to main content
Glama

RestaurantDoctorAI

Tip-out sheet

restaurantdoctor_tip_out
Read-onlyIdempotent

Works out how a restaurant shares tips, two ways, as the free tip-out sheet on restaurantdoctorai.com does. method percent: a server's tip-out to support roles, each a percentage of the server's net sales or tips, with the total tip-out, what the server keeps from their tips, and an error-level check when the tip-out is more than the tips. method pool: a tip pool shared by hours, with optional points for each role, rounded to the cent with the rounding remainder placed on the largest share. Takes the figures in any currency; a figure that isn't sent is never counted as 0. Returns the split, how it was worked out, the Department of Labor's published points on tips with their sources, and a link to the free tip-out sheet. It only works out a split from the numbers sent; it doesn't say whether a tip-out or a tip pool is allowed. The figures aren't stored; only an anonymous daily count of calculator runs is kept.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "method": "<method>"
    },
    "name": "restaurantdoctor_tip_out"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNo
poolNo
tipsNo
rolesNo
methodYespercent: one server's tip-out to support roles, each a % of the base. pool: a tip pool shared by hours, with optional points.
membersNo
baseKindNo

Output Schema

NameRequiredDescriptionDefault
lawYesThe Department of Labor's published points on tips and its state minimum wage page, each with its source.
linkYesThe free tip-out sheet, to print or download.
poolYes
notesYes
checksYesAn error when the tip-out is more than the tips.
methodYes
resultYesThe result in the sheet's words.
percentYes
freeCheckYes
workedOutYesHow it was worked out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the readOnly/idempotent/non-destructive annotations: rounding to the cent with remainder pushed onto the largest share, an error-level check when tip-out exceeds tips, currency-agnostic input, and the rule that an unsent figure is never counted as 0. It also discloses data handling ('figures aren't stored; only an anonymous daily count is kept'), which annotations do not cover.

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?

Front-loads the purpose and mode definitions before the return and privacy details, so the essential information comes first. It is dense but mostly earns its length; the recurring plug for the free tip-out sheet (mentioned twice) is mildly redundant.

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 7-parameter, single-required-field tool with an output schema, the description covers both modes, edge cases, and limitations well enough to invoke correctly without the output schema explaining returns. The only shortfall is the absence of sibling cross-references among the many restaurantdoctor_* calculators.

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?

The description explains how parameters interlock across modes — base vs. pool, baseKind determining whether percentages come off net sales or tips, and that omitted figures are ignored rather than zeroed. This adds real meaning beyond the field-level schema text, though it doesn't enumerate every constraint.

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 and resource — works out how a restaurant shares tips — and names the two modes (percent, pool) with a one-line definition of each. An agent can distinguish this from siblings like restaurantdoctor_fica_tip_credit without opening the schema.

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?

Gives clear context for each mode: percent is one server's tip-out to support roles off net sales or tips; pool is shared by hours with optional points. It also states a scope exclusion ('it doesn't say whether a tip-out or tip pool is allowed'), but never routes the agent to a sibling tool for related tip questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources