Skip to main content
Glama

The Doll Scout Home Tools

Add up landed cost · Second-hand cabinet accessory

tds_landed_boxed_resale
Read-onlyIdempotent

Add specified circulation costs and subtract the confirmed discount. Second-hand cabinet accessory. Marketplace service quote (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>",
      "marketServiceFeeCents": "<marketServiceFeeCents>"
    },
    "name": "tds_landed_boxed_resale"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYes
shippingCentsYes
unitPriceCentsYes
marketServiceFeeCentsYes
confirmedDiscountCentsYes

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 establish readOnly, idempotent, non-destructive behavior, so the description does not need to carry the safety profile. It adds that the operation is arithmetic and that amounts are in cents, but leaves the actual formula, rounding, and result format unexplained.

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?

Only three short sentences, with the action front-loaded. However, the second and third sentences are noun-phrase fragments whose contribution is unclear, so the structure is weaker than the low word count suggests.

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 financial calculation with no output schema, the definition should at minimum state the formula and the return value. It leaves both unclear and does not compensate for the complete lack of schema descriptions.

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 numeric parameters. The description gestures at 'circulation costs', 'confirmed discount', and 'marketplace service quote (cents)' but does not define unitPriceCents, quantity, shippingCents, or map them to the formula.

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 first sentence names an arithmetic operation (add costs, subtract discount) and the title supplies 'landed cost', so the broad purpose is inferable. But the description never clearly says what resource is being costed beyond the fragment 'Second-hand cabinet accessory', and it does not distinguish this from the many sibling tds_landed_* 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?

No when-to-use guidance, prerequisites, or alternatives are stated despite numerous sibling landed-cost tools. The fragments imply a narrow second-hand cabinet accessory context but do not help the agent choose this tool over alternatives.

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.