Skip to main content
Glama

Flooring carton order

bpj_material_floor_cartons
Read-onlyIdempotent

Calculate the carton count and ordered area for flooring with an explicit cutting allowance.

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>",
      "waste": "<waste>",
      "carton": "<carton>"
    },
    "name": "bpj_material_floor_cartons"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYes
wasteYes
cartonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare this as a safe, read-only, idempotent calculation tool, so the description's burden is lower. It adds that the waste allowance is treated as an 'explicit cutting allowance' and that the tool returns carton count and ordered area, but it does not disclose rounding behavior, the exact formula, or whether ordered area includes the allowance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no redundant wording. Every part of the sentence contributes to identifying the calculation and its flooring-specific scope.

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?

The description identifies the two expected outputs and the cutting-allowance concept, which is useful given there is no output schema. However, for a calculation tool it omits key behavioral details such as whether carton count is rounded up and how the waste percentage is applied, leaving meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It only loosely references 'cutting allowance' and 'carton count' without clarifying how 'area', 'waste', or 'carton coverage' are used together, leaving parameter meaning largely dependent on schema titles.

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 verb (calculate) and resource (carton count and ordered area for flooring), making the tool's function clear. It does not explicitly differentiate itself from sibling material calculators such as bpj_material_shipping_carton, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for flooring' implies a domain of use, but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. An agent must infer the selection criteria from the name and description alone.

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.