Skip to main content
Glama

The Doll Scout Home Tools

Estimate billable parcel weight · Market stock parcel

tds_billing_show_stock
Read-onlyIdempotent

Compare actual weight and dimensional weight under your quoted divisor and rounding increment. Market stock parcel. Quoted event stock 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>",
      "eventStockIncrementG": "<eventStockIncrementG>"
    },
    "name": "tds_billing_show_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossMassGYes
outerWidthCmYes
outerHeightCmYes
outerLengthCmYes
divisorCm3PerKgYes
eventStockIncrementGYes

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the comparison is against a quoted divisor and rounding increment, but it does not explain which result is selected, whether the larger value is billed, or how rounding is applied—behavior an estimating tool should disclose.

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?

The lead sentence is efficient and front-loaded, but the two trailing noun fragments ('Market stock parcel', 'Quoted event stock increment (g)') read as pasted labels that add no actionable information and blunt the structure.

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?

There is no output schema, yet the description never says what is returned—presumably a billable weight figure or the winning measurement—nor how the six required inputs combine. For a six-parameter, fully-required computation with no structured output documentation, this leaves a significant gap.

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 description coverage is 0% for six required parameters, so the description must carry the semantic load. It maps divisorCm3PerKg to 'quoted divisor' and eventStockIncrementG to 'rounding increment' (despite the confusing 'Quoted event stock increment (g)' fragment), while the dimension and mass parameters rely on their unit-bearing names.

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 first sentence states a specific operation: comparing actual weight against dimensional weight using a quoted divisor and rounding increment, which is enough to identify it as a billable-weight estimation tool. The trailing fragments 'Market stock parcel' and 'Quoted event stock increment (g)' are opaque and do not help distinguish it from the many sibling tds_billing_* tools.

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 versus alternatives, no prerequisites, and no exclusions. With a large family of sibling billing tools, an agent is left to guess which billing estimator applies to its situation.

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.