Skip to main content
Glama

The Doll Scout Home Tools

Add up landed cost · A collectible figure delivery

tds_landed_figurine
Read-onlyIdempotent

Add specified circulation costs and subtract the confirmed discount. A collectible figure delivery. Quoted parcel insurance (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>",
      "parcelInsuranceCents": "<parcelInsuranceCents>"
    },
    "name": "tds_landed_figurine"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYes
shippingCentsYes
unitPriceCentsYes
parcelInsuranceCentsYes
confirmedDiscountCentsYes

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the bar is lower. The description does add a little behavior: costs are summed and the confirmed discount is subtracted, and insurance is denominated in cents. It does not disclose the exact formula, rounding behavior, or what value comes back.

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?

It is short, but it is three disconnected fragments rather than a front-loaded explanation. 'A collectible figure delivery.' adds nothing about the operation and reads as filler between the two sentences that do carry meaning.

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?

Five required parameters, no output schema, and zero schema description coverage means the description had to explain both the computation and the inputs; it does neither. An agent cannot tell whether the return value is a total, a per-unit cost, or a breakdown, nor how quantity interacts with unit price.

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?

All five parameters are required with 0% schema description coverage, so the description carries the full burden and largely fails. Only parcelInsuranceCents gets meaning ('quoted parcel insurance (cents)'); quantity, unitPriceCents, shippingCents and confirmedDiscountCents are never explained, and the role of unitPriceCents as a per-unit multiplier is unstated.

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 description names an arithmetic operation (add costs, subtract discount) and a domain (a collectible figure delivery), so the general purpose is inferable. However, 'circulation costs' is not a term the schema uses, and the description never states that the result is a landed-cost total computed from unitPriceCents x quantity plus shipping and insurance minus discount. It also gives no differentiation from the many sibling tds_landed_* tools it sits beside.

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 which sibling to pick when landed cost is not what is wanted. The agent is left to infer the scenario entirely from the 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.