Skip to main content
Glama

The Doll Scout Home Tools

Add up landed cost · A framed print delivery

tds_landed_framed_print
Read-onlyIdempotent

Add specified circulation costs and subtract the confirmed discount. A framed print delivery. Declared handling 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>",
      "glassHandlingFeeCents": "<glassHandlingFeeCents>"
    },
    "name": "tds_landed_framed_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYes
shippingCentsYes
unitPriceCentsYes
glassHandlingFeeCentsYes
confirmedDiscountCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so the safety profile is covered. Beyond that, the description adds only a hint that the handling fee is 'declared' — it says nothing about the arithmetic performed, rounding, units of the result, or whether the output is a scalar total, which is the key behavior for a computation tool.

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, but two are bare fragments ('A framed print delivery.' and 'Declared handling fee (cents).') that read like filename-style labels rather than front-loaded guidance. Nothing is padded, yet the ordering buries the operative formula first without context.

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 an arithmetic tool with five mandatory numeric inputs, no output schema, and zero schema documentation, the description should state the exact computation and the shape of the result. It omits both, leaving an agent unable to verify what value comes back or how quantity interacts with unit price.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five required parameters, so the description must compensate and largely does not. It references the confirmed discount and the handling fee (in cents), covering at best two of five inputs, and never clarifies whether unitPriceCents is multiplied by quantity or how shippingCents enters the total.

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 gives a partial formula ('add specified circulation costs and subtract the confirmed discount'), which implies a landed-cost calculation, but 'circulation costs' is vague phrasing and the framed-print context comes only from the title fragment 'A framed print delivery.' An agent can guess it is a cost roll-up, yet cannot tell precisely which quantities are 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?

There is no indication of when to use this tool versus the many sibling landed-cost tools (tds_landed_art_tray, tds_landed_figurine, tds_billing_framed_art, etc.), no prerequisites, and no exclusions. The reader is left to infer usage entirely from 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.