Skip to main content
Glama

RestaurantDoctorAI

List a restaurant's deadlines

restaurantdoctor_deadlines
Read-onlyIdempotent

Lists a US restaurant's coming tax, payroll, license and permit deadlines, as the deadline calendar on restaurantdoctorai.com does: federal dates (payroll forms, tip reports, W-2s, 1099s, returns, estimated tax) and the state's (sales tax, unemployment reports, yearly reports, franchise taxes, minimum wage changes, liquor and health permit dates where one date applies to everyone), each moved for weekends and holidays by the agency's rule, with the rule, what a miss costs and the official source. A state date is given only where the state's own page confirms it; the rest come as what to check with the agency. Also the rules for each hire, and a link that opens the same calendar on the website, where the owner adds their own license and permit dates and gets free email reminders. Takes the state and yes/no answers, no names or emails; scope (federal or state) and withinDays (the next so many days) cut the list. Reminders, not legal or tax advice. The answers aren't stored; only an anonymous daily count of calendars 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": {
      "state": "<state>",
      "staff": "<staff>",
      "alcohol": "<alcohol>"
    },
    "name": "restaurantdoctor_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoA city with its own minimum wage, as an id like los-angeles or chicago; left out, the state's rate applies.
tipsNoCustomers usually tip the staff.
scopeNoOptional, to cut the list: federal (the IRS's and other federal dates only), state (the state's and the city's only) or all (the default). The rules for each hire are listed either way.
staffYesHas anyone on payroll.
stateYesThe restaurant's US state, two letters (DC for Washington DC).
formedNoThe month the LLC or corporation was formed with the state, YYYY-MM. Some states set the yearly report by it.
monthsNoHow many months ahead to list, 1 to 15 (default 3). The calendar runs to the end of 2027. withinDays, when sent, sets the window instead.
alcoholYesSells alcohol.
catererNoMainly catering or a food truck, not a restaurant or bar (OSHA's injury log).
businessNoHow the business is set up: sole (sole owner, no LLC), llc_single, llc_multi, partnership (no LLC), s_corp or c_corp. Decides the tax return and the state's yearly report. Left out, both return dates come with an "If".
depositsNoWho pays the payroll taxes to the IRS: provider (a payroll company), monthly (the owner, by the 15th), semiweekly (the owner, after each payday).
salesTaxNoHow often the state has the restaurant file sales tax (on its permit letter or state account).
bigTippedNoTipped, and staff worked more than 80 hours in total on a typical day last year, all locations together (Form 8027).
estimatedNoThe owner pays quarterly estimated tax on the business's profit.
fullTime50No50 or more full-time staff on average, counting part-timers' hours, related businesses together (ACA forms).
withinDaysNoOptional: only the dates in the next so many days, 1 to 460, from today in the state (7 for the coming week). Sent, it replaces months.
contractorsNoPays a contractor, or rent to a landlord that isn't a corporation, $2,000 or more a year (1099 forms).

Output Schema

NameRequiredDescriptionDefault
fromYesThe first day listed (today in the state), YYYY-MM-DD.
noteYes
stateYes
throughYesThe last day listed, YYYY-MM-DD.
eachHireYesRules that run each time the restaurant hires (or something happens), not on a date.
checkWithYesWhat we can't date for this owner: their own schedule or papers, or a state page not yet confirmed. No date here is guessed.
deadlinesYes
calendarUrlYesThe same calendar on restaurantdoctorai.com, where the owner can add the dates printed on their own licenses and permits and get email reminders or a calendar link, free.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / checkWith / description
      Previous value: -"What we can't date for this owner: their own schedule or papers, or a state page not yet confirmed. Never a guessed date."New value: +"What we can't date for this owner: their own schedule or papers, or a state page not yet confirmed. No date here is guessed."
  2. Changed8 schema fields changed
    • addedOutput schema / properties / deadlines / items / properties / appliesIf / anyOf
      Added value: +[
      +  {
      +    "description": "When an answer that decides it wasn't given: the condition it depends on.",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / deadlines / items / properties / appliesIf / description
      Removed value: -"When an answer that decides it wasn't given: the condition it depends on."
    • removedOutput schema / properties / deadlines / items / properties / appliesIf / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • addedOutput schema / properties / deadlines / items / properties / missCost / anyOf
      Added value: +[
      +  {
      +    "description": "What missing it costs, from its source, when the source says.",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / deadlines / items / properties / missCost / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • addedOutput schema / properties / deadlines / items / properties / movedFrom / anyOf
      Added value: +[
      +  {
      +    "description": "The date before a weekend or holiday moved it, and why.",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / deadlines / items / properties / movedFrom / description
      Removed value: -"The date before a weekend or holiday moved it, and why."
    • removedOutput schema / properties / deadlines / items / properties / movedFrom / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
  3. Changed3 schema fields changed
    • changedInput schema / properties / months / description
      Previous value: -"How many months ahead to list, 1 to 15 (default 3). The calendar runs to the end of 2027."New value: +"How many months ahead to list, 1 to 15 (default 3). The calendar runs to the end of 2027. withinDays, when sent, sets the window instead."
    • addedInput schema / properties / scope
      Added value: +{
      +  "description": "Optional, to cut the list: federal (the IRS's and other federal dates only), state (the state's and the city's only) or all (the default). The rules for each hire are listed either way.",
      +  "enum": [
      +    "all",
      +    "federal",
      +    "state"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / withinDays
      Added value: +{
      +  "description": "Optional: only the dates in the next so many days, 1 to 460, from today in the state (7 for the coming week). Sent, it replaces months.",
      +  "maximum": 460,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  4. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/idempotent/non-destructive): it discloses data provenance ('A state date is given only where the state's own page confirms it; the rest come as what to check with the agency'), what gets stored ('The answers aren't stored; only an anonymous daily count of calendars is kept'), and the week/holiday adjustment rule. This is exactly the kind of context structured fields cannot carry.

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 core purpose is front-loaded, but the single dense paragraph runs long and restates schema content ('Takes the state and yes/no answers... scope... withinDays cut the list') alongside genuinely new information. It is comprehensive rather than economical; trimming the input re-description would tighten it without losing meaning.

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 17 parameters, an output schema, and safety annotations already present, the description supplies the remaining pieces an agent needs: data provenance, fallback behavior when no state page confirms a date, privacy handling, and the website link. Nothing material is missing for correct invocation.

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% and every parameter carries a rich enum/detail description, so the schema does the heavy lifting. The description restates scope and withinDays generally but adds no syntax or format detail beyond what the schema already documents, making the baseline 3 appropriate.

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 (Lists) and resource (a US restaurant's coming tax, payroll, license and permit deadlines) and enumerates the concrete content (federal forms, state reports, holiday-moved dates). It is instantly distinguishable from every sibling, which are all cost/fee/knowledge calculators rather than a deadline calendar.

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 usage context: it names the driving inputs ('Takes the state and yes/no answers'), explains the scope/withinDays trimming, and sets expectations ('Reminders, not legal or tax advice'). It does not name an explicit alternative or a when-not-to-use condition, but no sibling overlaps this function, so the gap is minor.

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