Skip to main content
Glama

The Doll Scout Home Tools

Add up landed cost · Market stock delivery

tds_landed_event_stock
Read-onlyIdempotent

Add specified circulation costs and subtract the confirmed discount. Market stock delivery. Event receiving charge (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>",
      "eventReceivingCents": "<eventReceivingCents>"
    },
    "name": "tds_landed_event_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYes
shippingCentsYes
unitPriceCentsYes
eventReceivingCentsYes
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 this is a read-only, idempotent, non-destructive calculation, so safety behavior is covered. The description adds a partial arithmetic intent—adding costs and subtracting a confirmed discount—but does not state the full formula, rounding behavior, or output meaning. No contradiction with the read-only annotation exists.

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 enough, but it is fragmented: three staccato sentences, one of which ('Market stock delivery') reads like an unexplained label. It is not wasteful but lacks a clear front-loaded statement of the calculation performed.

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?

With five required parameters, zero schema description coverage, and no output schema, the description should carry more of the burden. It does not define the calculation sufficiently for an agent to confidently supply values or interpret the result.

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 explain five required parameters. It mentions a confirmed discount and an event receiving charge, but never clarifies unitPriceCents, quantity, or shippingCents, nor whether shipping is total or per unit. This leaves most parameter meaning undocumented.

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 title suggests a landed-cost calculation and the description mentions adding costs and subtracting a discount, but the body never clearly states that the tool computes total landed cost from unit price, quantity, shipping, and related charges. The fragment 'Market stock delivery' is ambiguous and does not distinguish it 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?

The description provides no guidance on when to use this calculator versus the numerous sibling landed-cost tools. It also omits prerequisites or context such as whether the values are per-unit or totals.

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.