Skip to main content
Glama

The Doll Scout Home Tools

Add up landed cost · Stationery order

tds_landed_stationery_order
Read-onlyIdempotent

Add specified circulation costs and subtract the confirmed discount. Stationery order. Supplier order fee (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>",
      "fixedSupplierFeeCents": "<fixedSupplierFeeCents>"
    },
    "name": "tds_landed_stationery_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYes
shippingCentsYes
unitPriceCentsYes
fixedSupplierFeeCentsYes
confirmedDiscountCentsYes

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 read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds the add-costs/subtract-discount direction and mentions the supplier fee, but omits rounding, output format, and whether quantity multiplies unit price.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short fragments are front-loaded with the calculation direction and contain no filler. The fragmentary structure and unexplained term 'circulation costs' are minor, but the definition is not padded.

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 calculation with no output schema and no parameter descriptions, the definition is incomplete: it does not specify the landed-cost formula, whether quantity multiplies unit price, rounding, or what value is returned.

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 coverage is 0%, so the description must define all five required parameters. It only vaguely points at confirmedDiscountCents and fixedSupplierFeeCents ('confirmed discount', 'Supplier order fee (cents)') and never explains unitPriceCents, quantity, or shippingCents, nor the formula tying them together.

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 description names an arithmetic operation (add costs, subtract discount) and scopes it to stationery orders, distinguishing it from other tds_landed_* siblings. 'Circulation costs' is imprecise and the formula is not explicit, but the purpose is still inferable.

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?

Only the phrase 'Stationery order' implies context; there is no explicit when-to-use, when-not-to-use, or alternative tool guidance, despite many sibling landed-cost tools.

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.