Skip to main content
Glama

The Doll Scout Home Tools

Estimate billable parcel weight · A protected photo book

tds_billing_photobook
Read-onlyIdempotent

Compare actual weight and dimensional weight under your quoted divisor and rounding increment. A protected photo book. Quoted photo book 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>",
      "photobookIncrementG": "<photobookIncrementG>"
    },
    "name": "tds_billing_photobook"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossMassGYes
outerWidthCmYes
outerHeightCmYes
outerLengthCmYes
divisorCm3PerKgYes
photobookIncrementGYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already establish this is a read-only, idempotent, closed-world, non-destructive operation, so the description carries a reduced burden. Beyond that, the description only implies a comparison happens but never says which weight governs billing, how the rounding increment is applied (up, nearest, per-unit), or whether both figures are reported. The phrases 'A protected photo book' and 'Quoted photo book increment (g).' are unexplained fragments that add no behavioral context.

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 one informative sentence is front-loaded, which is good, but it is followed by two sentence fragments that appear to be leaked title and schema text ('A protected photo book.', 'Quoted photo book increment (g).'). These consume space without earning it and actively confuse the reader about whether a description of the item or a parameter is being given.

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?

For a six-parameter pinned-apart calculator with no output schema, the description is not adequate: it explains neither the returned figures nor how the rounding/divisor interact, and it leaves every dimension parameter undocumented. The comparison framing gives a partial mental model, but an agent could not predict the result shape from this text alone.

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?

Six required parameters with 0% schema description coverage, so the description must compensate and it largely does not. It gestures at 'divisor' and 'rounding increment', but never maps these to divisorCm3PerKg or photobookIncrementG by name, and says nothing about the units/meaning of outerLengthCm, outerWidthCm, outerHeightCm or grossMassG.

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 opening sentence states a specific operation: comparing actual (gross) weight against dimensional weight under a quoted divisor and rounding increment. That is a real verb+resource, not a restatement of the name. It does not differentiate this from the many other tds_billing_* estimators, and the trailing fragments dilute rather than sharpen the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus another. Nothing tells the agent that this is the photobook-specific billing estimator rather than one of the sibling tds_billing_* tools, and no prerequisites or preconditions (e.g. having a quote with a divisor) are stated.

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.