Skip to main content
Glama

The Doll Scout Home Tools

Estimate billable parcel weight · Protected framed art

tds_billing_framed_art
Read-onlyIdempotent

Compare actual weight and dimensional weight under your quoted divisor and rounding increment. Protected framed art. Quoted framed art 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>",
      "framedArtIncrementG": "<framedArtIncrementG>"
    },
    "name": "tds_billing_framed_art"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossMassGYes
outerWidthCmYes
outerHeightCmYes
outerLengthCmYes
divisorCm3PerKgYes
framedArtIncrementGYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add computational context — and it does, by naming the divisor-based dimensional weight and a rounding increment in grams. However, it does not disclose the actual comparison rule (returns the greater of the two? both values? a boolean?) or the unit of the result. Given annotations carry the safety burden, this is adequate but incomplete.

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

Conciseness3/5

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

It is short and the core computation is front-loaded, which is good. But two of the three sentences are telegraphic fragments ('Protected framed art.', 'Quoted framed art increment (g).') and the last one reads as a parameter echo rather than a statement of behavior, so the structure is terse at the cost of clarity.

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?

For a six-parameter, all-required calculation tool with no output schema, the description leaves key questions open: what exactly is returned (billable grams, a comparison, a rounded value?) and in what unit. It also does not state whether outer dimensions define the volume used for dimensional weight. The result is a definition that is too thin for the tool's complexity even though annotations cover the safety side.

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 0%, so the description has to carry all parameter meaning. It does map three of the six inputs — grossMassG as 'actual weight', divisorCm3PerKg as the 'quoted divisor', and framedArtIncrementG as the 'quoted framed art increment (g)' — which is real added meaning. The three outer dimension parameters are only implied by 'dimensional weight', and how the increment is applied (round up/down/nearest) is unspecified, leaving half the surface to guesswork.

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 operation ('compare actual weight and dimensional weight') against a specific resource family ('protected framed art'), and the tag 'framed art' separates it from siblings such as tds_billing_flat_poster or tds_billing_photobook. What it never says outright is that the output is the billable/chargeable weight, so the goal is inferable rather than stated. Still, an agent can tell this is the framed-art billing-weight calculation.

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 when-to-use statement, no exclusion, and no routing to alternatives — the description never says whether this replaces or complements tds_landed_framed_print or tds_static_art_frame_height. The phrase 'under your quoted divisor' hints that contract-specific values must be supplied, but that is a prerequisite hint, not usage guidance. An agent must guess the calling context from the name and title.

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.