Skip to main content
Glama

The Doll Scout Home Tools

Add up landed cost · Document sleeve delivery

tds_landed_archival_sleeves
Read-onlyIdempotent

Add specified circulation costs and subtract the confirmed discount. Document sleeve delivery. Quote for reinforced packing (cents).

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": {
      "unitPriceCents": "<unitPriceCents>",
      "quantity": "<quantity>",
      "shippingCents": "<shippingCents>",
      "confirmedDiscountCents": "<confirmedDiscountCents>",
      "reinforcedPackingCents": "<reinforcedPackingCents>"
    },
    "name": "tds_landed_archival_sleeves"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYes
shippingCentsYes
unitPriceCentsYes
confirmedDiscountCentsYes
reinforcedPackingCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description usefully adds the arithmetic behavior (sum costs, subtract confirmed discount) and that packing is quoted in cents. It does not explain the output form, rounding, or what quantity contributes to the calculation.

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 front-loads the arithmetic, but the sentence "Document sleeve delivery" is opaque and arguably wasted, and "Quote for reinforced packing (cents)" dangles without tying back to the computation.

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 five-required-parameter read-only calculator with no output schema needs the description to pin down the formula and units; instead it leaves quantity and two of the cost inputs unexplained and offers no return-value context, so an agent cannot confidently predict the result.

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 five required parameters, so the description carries the full burden. It hints at discounts and reinforced packing and the cents unit, but never mentions quantity, unitPriceCents, or shippingCents, and does not clarify how the inputs combine into landed cost.

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 verbs "Add" and "subtract" plus the title indicate a landed-cost computation for archival sleeves, which is more specific than the bare name. However, "Document sleeve delivery" and "Quote for reinforced packing" read as loosely related fragments rather than a coherent statement of what the tool returns, and nothing distinguishes it from the many sibling tds_landed_* costing 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 when-to-use guidance, no prerequisites, and no mention of any alternative among the numerous sibling costing tools (tds_threshold_*, tds_budget_*, other tds_landed_*). An agent must guess whether this tool or a sibling is the right one.

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.