Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

装修预算测算与报价核价

zhuangxiu-budget

装修预算测算与报价核价:输入建筑面积、档次、城市等级,出总价区间 + 9 项分项金额 + 每平米单价,用来判断装修公司报价是否离谱、谈判时心里有锚。附三个最常见的增项黑洞提醒。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "area": "<area>",
      "tier": "<tier>",
      "cityLevel": "<cityLevel>"
    },
    "name": "zhuangxiu-budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYes建筑面积(㎡)
tierYesbasic(简装)/ mid(中档)/ high(高档)
cityLevelYes城市等级 1-4(1=一线)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and explains that the tool returns a deterministic calculation result with supporting basis, including a total price range, 9 itemized amounts, per-square-meter price, and three common add-on pitfalls. It could say more about output format or limitations, but for a low-risk calculator it discloses the key behavioral traits.

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 description is front-loaded with purpose, inputs, and outputs, and most sentences earn their place by explaining use and return value. The phrase '传入参数对象,返回确定性计算结果与依据' is somewhat generic filler, preventing a perfect score.

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?

There is no output schema, so the description usefully enumerates the return contents: total range, 9 itemized amounts, per-square-meter price, and add-on reminders. It is nearly complete for a simple 3-parameter calculator, though it omits details such as currency or exact output structure.

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 the schema already documents area, tier values, and city level. The description restates the same three inputs but adds no additional parameter-level semantics, making the baseline 3 appropriate.

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 states a specific calculation task: input building area, tier, and city level to produce a total price range, 9 itemized amounts, and per-square-meter price. It clearly conveys the tool's purpose as budget estimation and quote checking, though it does not explicitly name or distinguish itself from sibling tools such as decoration-contract.

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 a clear usage context: use when the model's arithmetic is unstable or regulatory standards are error-prone, to obtain an accurate answer. It does not specify when not to use it or name alternative sibling tools, but the intended scenario is explicit enough for selection.

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.