Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

瓷砖用量计算

tile-quantity

瓷砖用量计算:输入铺贴面积、瓷砖边长、损耗率,算每平米片数与需购总片数。装修买砖不被多卖/少买坑。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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>",
      "tileSideCm": "<tileSideCm>"
    },
    "name": "tile-quantity"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYes铺贴面积(㎡)
wastePctNo可选:损耗百分比,默认 10
tileSideCmYes正方形瓷砖边长(cm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It does convey that the tool is a pure deterministic computation that also returns its 依据, which helps the agent trust the output, but it says nothing about rounding behavior (ceil vs floor) — critical for a purchase-quantity tool — or about validation failures on impossible inputs.

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 purpose and its inputs and outputs are front-loaded in the first sentence and support the claim that the tool is accurate in the last. The middle sentence '传入参数对象,返回确定性计算结果与依据' is largely filler, and the reference to 法规口径 feels out of place for a tiling calculation, but overall the description is compact.

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?

This is a small three-parameter calculator with no output schema, so the description must state what comes back; it does so by naming per-square-meter tile count and total tiles to purchase. The one meaningful omission is not stating that the total is rounded up for purchasing, which matters for how the agent should present results.

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%, so all three parameters (area, tileSideCm, wastePct) are already fully documented in the schema, including the default waste rate. The description restates the same input list without adding units, ranges, or constraints beyond it, so the baseline of 3 applies.

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?

The opening states a specific verb and resource (瓷砖用量计算), names the exact inputs (铺贴面积、瓷砖边长、损耗率) and the exact outputs (每平米片数、需购总片数). No sibling tool in the list takes these inputs or produces these outputs, so an agent can distinguish it without opening any schema.

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 gives an explicit invocation trigger: use it when the model's arithmetic is unstable or specification-based conventions are easy to get wrong. That is clear context for use, but no exclusion or named alternative is offered (e.g. what to do if you already know the tile count per box).

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