Skip to main content
Glama

The Doll Scout Home Tools

Estimate billable parcel weight · A boxed display case

tds_billing_display_carton
Read-onlyIdempotent

Compare actual weight and dimensional weight under your quoted divisor and rounding increment. A boxed display case. Quoted display parcel increment (g).

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": {
      "outerLengthCm": "<outerLengthCm>",
      "outerWidthCm": "<outerWidthCm>",
      "outerHeightCm": "<outerHeightCm>",
      "grossMassG": "<grossMassG>",
      "divisorCm3PerKg": "<divisorCm3PerKg>",
      "displayCartonRoundingG": "<displayCartonRoundingG>"
    },
    "name": "tds_billing_display_carton"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossMassGYes
outerWidthCmYes
outerHeightCmYes
outerLengthCmYes
divisorCm3PerKgYes
displayCartonRoundingGYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. Beyond that the description adds little: it does not disclose the return shape (whether both weights, the max, or only the billable value are returned), the direction of the rounding (ceil to the increment), or units for the dimensional result.

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

Conciseness2/5

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

The first sentence is well-formed and front-loaded, but the remaining sentences are disconnected noun fragments that add no information and read like scraped labels. A short description is fine; here the brevity comes from missing content rather than economy.

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

Completeness2/5

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

With six required parameters, zero schema descriptions, and no output schema, the description needed to explain both the calculation and the per-parameter roles. It leaves the computation path and the return value ambiguous, so an agent could invoke it with correct types but misunderstood semantics (e.g., wrong rounding direction).

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% across six required parameters, so the description carries the full burden and does not meet it. It loosely gestures at divisorCm3PerKg ("quoted divisor") and displayCartonRoundingG ("rounding increment"), but says nothing about outerLengthCm/outerWidthCm/outerHeightCm forming the volume, about grossMassG being the actual-weight input, or about allowable units and bounds.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a real verb and resource set: "Compare actual weight and dimensional weight under your quoted divisor and rounding increment." However, the two trailing fragments ("A boxed display case." and "Quoted display parcel increment (g).") restate the title rather than sharpen the purpose, and the description never says the tool outputs a billable/chargeable weight, which is only inferable from the title.

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?

There is no statement of when to use this tool, no preconditions (e.g., that the divisor and rounding increment must come from the quote), and no mention of any sibling such as tds_ornament_carton_run or tds_threshold_carton_inserts. The agent must infer the billing context entirely.

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.