Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

盈亏平衡点(保本销量)计算

breakeven-point

盈亏平衡点(保本销量)计算:输入固定成本、单价、单位变动成本,算出卖多少件才不亏、对应的保本营业额。开店前判断"这生意能不能回本"的第一步。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "fixedCost": "<fixedCost>",
      "unitPrice": "<unitPrice>",
      "unitVarCost": "<unitVarCost>"
    },
    "name": "breakeven-point"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixedCostYes固定成本(元)
unitPriceYes单价(元)
unitVarCostYes单位变动成本(元)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 burden. It does disclose that the result is deterministic and includes its 依据, which is useful context that the structured fields do not provide, but it stays silent about behaviour when unitPrice ≤ unitVarCost (the division-by-zero or impossible break-even case) and about rounding, currency and tax conventions, all of which matter in a money calculator.

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?

The definition is front-loaded: the purpose and outputs come first, followed by the context and scenarios. It is somewhat padded by the marketing-style line about judging whether the business can recoup its costs before opening, which is rhetorical rather than operational.

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

Completeness3/5

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

For a simple three-parameter calculator with no output schema, the description usefully states what is returned (the break-even volume and the corresponding break-even revenue), which compensates for the missing output schema. However, it omits the edge-case behaviour described above and the output precision, so it is still short of complete.

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%, and all three parameters carry descriptions naming units (元), so the schema does the documentation work. The description only restates the same three input names in Chinese with no extra meaning, constraints or acceptable ranges, which is the baseline.

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 title and description state a specific calculation with clearly named inputs 固定成本、单价、单位变动成本 and clearly named outputs 保本销量和保本营业额, so an agent can tell exactly what it gets. However, the description never distinguishes the tool from the numeric siblings, such as gross-margin or discount-price, which are the nearest neighbours.

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?

The description provides real usage context: it is the first step in judging whether a store can break even before opening, and it should be called when mental arithmetic is unreliable or when regulatory conventions are error-prone. It never says when *not* to use the tool, and it never points to an alternative, so the definition earns 4 rather than 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