Skip to main content
Glama

The Doll Scout Home Tools

Add up landed cost · A storage cart delivery

tds_landed_storage_cart
Read-onlyIdempotent

Add specified circulation costs and subtract the confirmed discount. A storage cart delivery. Quoted floor delivery extra (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>",
      "floorCarryFeeCents": "<floorCarryFeeCents>"
    },
    "name": "tds_landed_storage_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYes
shippingCentsYes
unitPriceCentsYes
floorCarryFeeCentsYes
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 declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so safety behavior is covered. The description adds some calculation behavior by saying costs are added and the confirmed discount subtracted, plus that the floor delivery fee is quoted in cents, but it omits details such as rounding, currency handling, and what the computed 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 definition is short and front-loads the calculation, but the sentence 'A storage cart delivery.' is fragmentary and adds little, while 'Quoted floor delivery extra (cents).' is terse to the point of ambiguity. It is not bloated, but the structure could be clearer.

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 tool with no output schema, the description does not fully specify the formula, how quantity and unit price interact, or the return value. Annotations cover the read-only and idempotent nature, but the calculation semantics remain under-described.

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 for all five required parameters. It only loosely maps 'confirmed discount' to confirmedDiscountCents and 'floor delivery extra' to floorCarryFeeCents, while leaving unitPriceCents, quantity, and shippingCents unexplained, including the likely quantity-times-unit-price calculation.

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 states an arithmetic action ('Add specified circulation costs and subtract the confirmed discount') and ties it to 'A storage cart delivery', so the general purpose is inferable. However, 'circulation costs' is vague, the delivery sentence is fragmentary, and there is no explicit differentiation from the many sibling landed-cost 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 explicit guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The calculation context only implies usage and leaves the agent to infer which landed-cost scenario this tool covers.

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.