Skip to main content
Glama

The Doll Scout Home Tools

Compare a shipping threshold · Cloth cover shipping

tds_threshold_cloth_cover_order
Read-onlyIdempotent

Compare your cart and the cart after adding a needed item under a quoted shipping rule. Cloth cover shipping. Price of a necessary extra cover (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>",
      "coverOrderTopUpCents": "<coverOrderTopUpCents>"
    },
    "name": "tds_threshold_cloth_cover_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
cartCentsYes
coverOrderTopUpCentsYes
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?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the operation compares the current cart with the cart after adding an item under a quoted shipping rule, but it does not explain the result, threshold behavior, or what the comparison actually returns.

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 and the comparison operation is front-loaded, but "Cloth cover shipping." is a cryptic fragment that adds little clarity. The final sentence explains one parameter but reads as a disconnected addendum rather than a coherent specification.

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 threshold-comparison tool with no output schema, the description does not explain the return value or how the quoted shipping rule is applied. It also leaves four required parameters undocumented, making the definition insufficient for confident invocation.

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 carry the burden of explaining the five required parameters. It clarifies only one input, the price of a necessary extra cover in cents, and leaves cartCents, shippingThresholdCents, belowThresholdShippingCents, and atThresholdShippingCents to be inferred from their names alone.

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 indicates a comparison between the current cart and the cart after adding a needed item under a quoted shipping rule, which is a recognizable operation. However, phrases like "Cloth cover shipping" and "Price of a necessary extra cover" are cryptic and do not clearly establish how this tool differs from other threshold-related 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 guidance, no prerequisites, and no alternatives or exclusions. The description only implies that this is for comparing shipping thresholds, leaving the agent to infer the appropriate context.

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.