Skip to main content
Glama

The Doll Scout Home Tools

Compare unit offers · Card dividers

tds_unit_price_card_dividers
Read-onlyIdempotent

Compare delivered prices in one currency using matching quantity units and an explicit adjustment. Card dividers. Offer B divider labels (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": {
      "offerACents": "<offerACents>",
      "offerAQuantity": "<offerAQuantity>",
      "offerBCents": "<offerBCents>",
      "offerBQuantity": "<offerBQuantity>",
      "offerBDividerLabelsCents": "<offerBDividerLabelsCents>"
    },
    "name": "tds_unit_price_card_dividers"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerACentsYes
offerBCentsYes
offerAQuantityYes
offerBQuantityYes
offerBDividerLabelsCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already establish that this is a safe read-only, idempotent, closed-world operation. The description adds useful behavioral context: prices must be delivered prices in one currency, quantities must use matching units, and an explicit adjustment applies. It still does not explain the adjustment mechanics or what the comparison 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 definition is short and the main comparison purpose is front-loaded. But the two trailing fragments, "Card dividers" and "Offer B divider labels (cents)," are cryptic and do not form a clear explanation of the calculation.

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 tool with five required parameters, zero schema descriptions, and no output schema, this description is too thin. It does not explain the parameter meanings, the adjustment mechanism, or what result the caller should expect.

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 define the five required parameters, but it only mentions "Offer B divider labels (cents)" and generally references matching quantity units and one currency. It does not explain offerACents, offerBCents, offerAQuantity, offerBQuantity, or how offerBDividerLabelsCents affects the comparison.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific comparison action: comparing delivered prices in one currency with matching quantity units and an explicit adjustment, scoped to card dividers. This is more than a tautology and the category helps distinguish it from sibling unit-price tools. However, phrases like "explicit adjustment" and "Offer B divider labels" remain vague about the exact computation.

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 statement of when not to use this tool, and no named alternative. The category "Card dividers" implies it is for that product type, but the agent must infer that from the fragment rather than from stated guidance.

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.