Skip to main content
Glama

The Doll Scout Home Tools

Compare a shipping threshold · Photo card shipping

tds_threshold_photo_cards
Read-onlyIdempotent

Compare your cart and the cart after adding a needed item under a quoted shipping rule. Photo card shipping. Price of a needed card pack (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": {
      "cartCents": "<cartCents>",
      "shippingThresholdCents": "<shippingThresholdCents>",
      "belowThresholdShippingCents": "<belowThresholdShippingCents>",
      "atThresholdShippingCents": "<atThresholdShippingCents>",
      "photoCardPackCents": "<photoCardPackCents>"
    },
    "name": "tds_threshold_photo_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
cartCentsYes
photoCardPackCentsYes
shippingThresholdCentsYes
atThresholdShippingCentsYes
belowThresholdShippingCentsYes

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, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds that the tool performs a comparative computation rather than a lookup, but never states what the comparison yields (e.g., the break-even quantity or savings), and there is no output schema to fill that gap.

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?

Three short sentences with no padding, and the core action is stated first. However, the second and third sentences are telegraphic fragments ("Photo card shipping." / "Price of a needed card pack (cents).") that read as trimmed metadata rather than organized explanation, so structure is minimal rather than efficient.

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 inputs, no output schema, and no annotation coverage of return behavior, the description should clarify what the agent gets back and how the shipping-rule inputs interact. It covers neither, leaving an agent unable to predict the result shape or interpret the comparison.

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 parameters, so the description carries the full burden and largely fails. It only gestures at one parameter via "Price of a needed card pack (cents)," and never explains the relationship among cartCents, shippingThresholdCents, belowThresholdShippingCents, and atThresholdShippingCents beyond what their names suggest.

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 names a comparison operation (cart vs. cart after adding an item) and scopes it to shipping thresholds, so the general idea is recoverable. But the phrasing "Compare your cart and the cart after adding a needed item under a quoted shipping rule" is convoluted, and "Photo card shipping" reads as a tag rather than a purpose statement. It only weakly separates this from the many other tds_threshold_* siblings.

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 when-to-use or when-not-to-use guidance, and no named alternative among the numerous threshold tools (archival sleeves, binder pages, carton inserts, etc.). An agent must infer from the words "Photo card" that this instance applies to photo-card shipping only, which is implied at best.

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.