Skip to main content
Glama

The Doll Scout Home Tools

Add up landed cost · Archival trays delivery

tds_landed_art_tray
Read-onlyIdempotent

Add specified circulation costs and subtract the confirmed discount. Archival trays delivery. Paid corner protection (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>",
      "cornerProtectionFeeCents": "<cornerProtectionFeeCents>"
    },
    "name": "tds_landed_art_tray"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYes
shippingCentsYes
unitPriceCentsYes
confirmedDiscountCentsYes
cornerProtectionFeeCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation. The description adds some behavioral context by stating that costs are summed and the confirmed discount is subtracted, and by clarifying that corner protection is a paid fee. It does not cover rounding rules, whether the discount applies before or after fees, or what the result represents.

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 description is short and front-loads the core add-costs/subtract-discount behavior. However, the second and third fragments are abrupt, and the unclear term 'circulation costs' weakens otherwise efficient wording.

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 five-parameter required calculation tool with no output schema and no parameter documentation, the description is too thin. It does not state the actual landed-cost formula, how quantity and unit price participate, or what the returned value will be.

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%, so the description must compensate, but it only partially maps to the parameters. It references confirmed discount and paid corner protection, and vaguely implies shipping or circulation costs, but does not explain unitPriceCents or quantity or how they combine into landed cost.

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 title and description make clear this computes a landed cost for archival trays delivery by adding costs and subtracting a confirmed discount. It also distinguishes the item domain from sibling landed-cost tools. However, the phrase 'circulation costs' is vague and slightly muddies what is being summed.

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?

The description gives no explicit when-to-use guidance, no exclusions, and no comparison with other landed-cost siblings. Usage is only implied by the 'Archival trays delivery' phrase and the tool name.

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.