Skip to main content
Glama

RestaurantDoctorAI

Card fees check

restaurantdoctor_card_fees
Read-onlyIdempotent

Checks a US restaurant's card processing fees for one month, as the free card fees check on restaurantdoctorai.com does: the cost per 100 dollars of card sales (the effective rate), against a dated fair range for that type of restaurant (an estimate of a competitive interchange-plus account from Visa's published restaurant interchange, network fees and a fair markup); how far above it the fees are, a month and a year; how they compare with Square's, Toast's, Clover's or Stripe's published rate; what's realistic for that processor, words to read out to it, the fees to question on the statement by name, and the caveats. It answers whether card fees are too high, what the effective rate is, and what to ask the processor. It needs the month's total card sales and total card fees from the processor's statement (every fee, monthly and annual ones included), who processes the cards and what kind of restaurant it is; the number of card sales or the average sale narrows it. A figure that isn't sent is never counted as 0. It doesn't read statements, contact a processor or take payment. Returns the result, how it was worked out, and a link that opens the same check with the figures filled in. 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": {
      "processor": "<processor>",
      "format": "<format>"
    },
    "name": "restaurantdoctor_card_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYesThe type of restaurant, which sets the likely mix of debit and credit cards: quick_service = Quick service (Counter or kiosk, fast turnover); fast_casual = Fast casual (Order at the counter, served at the table); full_service = Full service / casual dining (Servers, moderate check); fine_dining = Fine dining (Chef-driven, higher check); bar_lounge = Bar, taproom or lounge (Drinks are about half of sales or more); cafe = Café or coffee shop (Drinks lead, with pastries and light food).
cardCountNo
cardSalesNo
processorYesWho processes the cards (the name at the top of the statement): bank = a bank or independent processor; other = another processor, or not sure.
totalFeesNo
pricingModelNo
averageTicketNo

Output Schema

NameRequiredDescriptionDefault
askYesWords the owner can read out to the processor.
fairYesWhat a competitive interchange-plus account would cost, per $100: an estimate, not a published price.
linkYesOpens the check on the website with these figures filled in.
planYes
checksYesFigures that look like a slip. They don't block the result.
formatYes
resultYesThe page's words, in its order.
caveatsYes
sourcesYes
verdictYes
aboveTopYesFees above the range's top, whole dollars; 0 unless above it.
saleFromYes
cardCountYes
cardSalesYesUS dollars, like every amount here.
freeCheckYes
processorYes
realisticYes
totalFeesYes
workedOutYes
costPer100YesTotal fees ÷ card sales × 100: the cost per $100 of card sales, also the effective rate in %.
aboveMiddleYesThe same above its middle.
averageSaleYes
pricingModelYes
overTopPer100YesDollars per $100 above the range's top; 0 unless above it.
feesToQuestionYesBy the names statements print.
yearlyCardSalesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / format / description
      Previous value: -"The type of restaurant, which sets the likely mix of debit and credit cards: quick_service = Quick service (Counter or kiosk, fast turnover); fast_casual = Fast casual (Order at the counter, food brought to the table); full_service = Full service / casual dining (Servers, moderate check); fine_dining = Fine dining (Chef-driven, higher check); bar_lounge = Bar, taproom or lounge (Drinks are about half of sales or more); cafe = Café or coffee shop (Drinks lead, with pastries and light food)."New value: +"The type of restaurant, which sets the likely mix of debit and credit cards: quick_service = Quick service (Counter or kiosk, fast turnover); fast_casual = Fast casual (Order at the counter, served at the table); full_service = Full service / casual dining (Servers, moderate check); fine_dining = Fine dining (Chef-driven, higher check); bar_lounge = Bar, taproom or lounge (Drinks are about half of sales or more); cafe = Café or coffee shop (Drinks lead, with pastries and light food)."
  2. Changed3 schema fields changed
    • changedInput schema / properties / format / description
      Previous value: -"The type of restaurant, which sets the likely mix of debit and credit cards: quick_service = Quick service (Counter or kiosk, fast turnover); fast_casual = Fast casual (Order at the counter, food brought to the table); full_service = Full service / casual dining (Servers, moderate check); fine_dining = Fine dining (Chef-driven, higher check); bar_lounge = Bar, taproom or lounge (Drinks are about half of sales or more)."New value: +"The type of restaurant, which sets the likely mix of debit and credit cards: quick_service = Quick service (Counter or kiosk, fast turnover); fast_casual = Fast casual (Order at the counter, food brought to the table); full_service = Full service / casual dining (Servers, moderate check); fine_dining = Fine dining (Chef-driven, higher check); bar_lounge = Bar, taproom or lounge (Drinks are about half of sales or more); cafe = Café or coffee shop (Drinks lead, with pastries and light food)."
    • changedInput schema / properties / format / enum
      Previous value: -[
      -  "quick_service",
      -  "fast_casual",
      -  "full_service",
      -  "fine_dining",
      -  "bar_lounge"
      -]New value: +[
      +  "quick_service",
      +  "fast_casual",
      +  "full_service",
      +  "fine_dining",
      +  "bar_lounge",
      +  "cafe"
      +]
    • changedOutput schema / properties / format / enum
      Previous value: -[
      -  "quick_service",
      -  "fast_casual",
      -  "full_service",
      -  "fine_dining",
      -  "bar_lounge"
      -]New value: +[
      +  "quick_service",
      +  "fast_casual",
      +  "full_service",
      +  "fine_dining",
      +  "bar_lounge",
      +  "cafe"
      +]
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations' read-only/idempotent profile, it discloses that a missing figure is never counted as 0, what it returns (result, workings, prefilled link), retention behavior (figures not stored, only an anonymous daily run count), and what it will not do. Those are real behavioral facts an agent could not infer from annotations or schema.

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

Conciseness3/5

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

The purpose is front-loaded, but the first sentence is a very long chain of parentheticals listing outputs, and later content (fair-range methodology, privacy) is interleaved in the same dense paragraph. Nearly every clause carries information, yet the heavy nesting makes it slower to scan than warranted.

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

Completeness5/5

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

With 7 parameters, an output schema, and a multi-part calculation, the description covers required inputs, optional narrowing inputs, non-goals, missing-data behavior, and data retention. An agent has everything needed to decide to call it and to know what it will do with incomplete input.

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 coverage is low (29%), and the description compensates by explaining which figures are needed and why: total card sales and total card fees (every fee, monthly and annual included), processor, restaurant type, with card count or average sale only narrowing the range. It omits pricingModel entirely, which the schema says changes the advice, so one parameter is left to the schema alone.

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 — checks a US restaurant's card processing fees for one month — and immediately names the concrete outputs (effective rate vs. a dated fair range, gap in dollars per month and year, comparison to Square/Toast/Clover/Stripe). That is clearly distinguishable from siblings like booking_fees or delivery_price by domain and by the fair-range comparison it performs.

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?

It says when it applies (one month, US restaurant, needs total card sales and total card fees from the statement) and bounds it explicitly: it doesn't read statements, contact a processor or take payment. It never routes the agent to a sibling, e.g. that booking fees are a different check, so it stops short of a 5.

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