Skip to main content
Glama

The Doll Scout Home Tools

Estimate billable parcel weight · A parcel of binders

tds_billing_binders_combined
Read-onlyIdempotent

Compare actual weight and dimensional weight under your quoted divisor and rounding increment. A parcel of binders. Quoted binder batch 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>",
      "binderBatchIncrementG": "<binderBatchIncrementG>"
    },
    "name": "tds_billing_binders_combined"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossMassGYes
outerWidthCmYes
outerHeightCmYes
outerLengthCmYes
divisorCm3PerKgYes
binderBatchIncrementGYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile carries no burden on the description. Beyond that, the description adds only that a divisor and rounding increment influence the result, but never states the rounding direction, which of the two weights becomes billable, or whether a surcharge applies — meaningful omissions for a pricing calculation; a 3 reflects partial credit because the safe-read trait is fully covered by annotations.

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?

Three sentences, two of which are sentence fragments carrying no operational content. The front-loaded sentence is fine, but the trailing fragments pad the definition without adding information, and there is no structure (bullets, sequencing) for a six-parameter calculation.

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?

A weight-versus-dimensional-weight calculator with no output schema and 0% parameter documentation needs the description to explain the computation and result, and this one does not. An agent cannot tell from the text what value comes back or how rounding is applied.

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 must compensate and largely fails. It gestures at the divisor and the rounding increment but renames the latter as "quoted binder batch increment," which obscures rather than clarifies, and it never mentions the four dimension parameters or grossMassG, nor the minimum-1 constraints.

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 first sentence names a specific operation: comparing actual weight against dimensional weight using a quoted divisor and a rounding increment, which reads as a billable-weight estimator. However, the two trailing fragments ("A parcel of binders." and "Quoted binder batch increment (g).") are theme filler that restate the domain and a parameter name rather than sharpen scope, and nothing distinguishes this from billing siblings such as tds_billing_display_carton or tds_billing_flat_poster.

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?

No guidance on when to use this versus the other billing estimators in the sibling list, and no prerequisites stated. An agent must infer from the name alone that this applies to binder parcels rather than cartons, posters, or framed art.

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.