Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

餐饮翻台率与营业额测算

table-turnover

餐饮翻台率与营业额测算:输入桌数、翻台次数、每桌座位、客单价,估算满座口径下的接待人次与营业额上限。餐饮开店测算翻台模型。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "tables": "<tables>",
      "turns": "<turns>",
      "seatsPerTable": "<seatsPerTable>",
      "avgSpend": "<avgSpend>"
    },
    "name": "table-turnover"
  }
}

Input Schema

NameRequiredDescriptionDefault
turnsYes全天翻台次数
tablesYes桌数
avgSpendYes客单价(元)
seatsPerTableYes每桌座位数

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two useful traits — the result is deterministic ('确定性计算结果') and it returns the 依据 behind the number — and it flags the 满座口径 assumption, which materially changes how the outputs should be read. It still omits edge-case behavior (e.g. what happens with non-integer turns or zero seats) and any sign the tool is side-effect free beyond the word '计算'.

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?

Purpose and inputs are front-loaded in the first sentence, and the whole definition is short. Minor waste in the standalone keyword fragment '餐饮开店测算翻台模型。' and in repeating the parameter list the schema already carries, but nothing obscures the core meaning.

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?

With four required parameters and no output schema, the description does the necessary work: it states what the returned 接待人次 and 营业额上限 represent and that a rationale accompanies them. Combined with the explicit full-occupancy assumption, an agent has enough to call this correctly and interpret the result. Missing only failure/edge-case behavior.

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 description coverage is 100%, so all four parameters are already documented with units (元) and meaning (全天翻台次数). The description re-lists the same four inputs without adding syntax, ranges, or units beyond the schema. The only added meaning is the 满座口径 framing, which is baseline-level value.

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 names a concrete computation — 翻台率/营业额测算 — and enumerates exactly which inputs drive it (桌数, 翻台次数, 每桌座位, 客单价) plus the two outputs (接待人次, 营业额上限) under a stated 满座口径. An agent knows precisely what this tool calculates. It stops short of a 5 because it never distinguishes itself from adjacent finance-model siblings such as breakeven-point or gross-margin.

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?

It offers a usage condition: call it when the model's arithmetic is unstable or regulatory interpretation is easily wrong. That is an explicit when-to-use, but it is generic boilerplate that could be pasted onto any tool in this family. There is no when-not guidance, no prerequisite context, and no named alternative for the cases this tool does not cover.

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