Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

菜单定价与保本测算

menu-pricing

菜单定价与保本测算:餐饮/奶茶店定菜单必备:输入单份食材成本和目标毛利率,算出建议售价;再填月固定成本,算出每月/每天要卖多少份才保本。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "cost": "<cost>",
      "targetMargin": "<targetMargin>",
      "fixedCost": "<fixedCost>"
    },
    "name": "menu-pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYes单份食材/原料成本(元)
fixedCostYes月固定成本(元,可填 0)
targetMarginYes目标毛利率(如 65 表示 65%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 that the tool returns '确定性计算结果与依据' (deterministic results plus the basis for them), which is useful transparency about output nature. It says nothing about edge cases — a 100% target margin, fixedCost=0 (which makes break-even undefined), assumed day-count for the daily figure, or validation errors — which is a meaningful gap for a pure calculation tool.

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?

Structure is front-loaded: title-purpose, then the two-step computation with its inputs, then the return contract, then the usage condition. Nearly every clause carries information. Minor padding exists in the marketing aside '餐饮/奶茶店定菜单必备' and the slightly misplaced '法规口径易错' reference, which is not obviously relevant to menu pricing.

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 three required parameters and no output schema, the description must convey what comes back, and it does: a suggested price plus break-even units per month and per day, along with the reasoning basis. What remains unstated is the convention behind the daily figure (e.g., 30-day month) and whether cost is per portion before or after waste. Those are small but real gaps for a calculator an agent will rely on for exact numbers.

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 already 100%, so the baseline is 3. The description goes further by mapping each input to its role in the computation: cost and targetMargin produce the suggested price; fixedCost additionally unlocks the monthly/daily break-even volume. That derivational context is not visible in the schema. It does not, however, clarify ambiguous input semantics such as whether targetMargin is a whole number like 65 or a fraction.

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 specific verb-and-resource pair: it takes per-portion ingredient cost and a target margin, computes a suggested selling price, then uses monthly fixed cost to compute the break-even volume per month/day. It is clear what the tool does and how the two computations chain. It does not name or distinguish itself from siblings such as breakeven-point or gross-margin, so it falls short of a 5.

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 gives an explicit usage context: '餐饮/奶茶店定菜单必备' plus '适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案' — i.e., call this tool when you need a reliable deterministic answer instead of model arithmetic. That is a clear when-to-use signal. There are no when-not conditions and no named alternative tools, 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