Skip to main content
Glama

The Doll Scout Home Tools

Compare unit offers · Display stands

tds_unit_price_display_stands
Read-onlyIdempotent

Compare delivered prices in one currency using matching quantity units and an explicit adjustment. Display stands. Offer B base plate adjustment (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>",
      "offerBBasePlateCents": "<offerBBasePlateCents>"
    },
    "name": "tds_unit_price_display_stands"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerACentsYes
offerBCentsYes
offerAQuantityYes
offerBQuantityYes
offerBBasePlateCentsYes

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description does add real behavioral constraints beyond that: a single currency is assumed, quantities must be expressed in matching units, and an 'explicit adjustment' is applied. However it never says the result is a comparison outcome (which offer wins, or the delta), leaving the tool's actual behavior partly opaque.

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, front-loaded with the core action, so it is not bloated. But the terseness tips into cryptic ('an explicit adjustment' before the adjustment is named) and the isolated 'Display stands' sentence carries no information; economy here costs comprehension.

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 numeric inputs, no output schema, and 0% parameter documentation, the description should carry the math and the return shape — it carries neither. An agent can guess the parameters' meaning but cannot tell what the tool returns (a winner, a delta, both unit prices) or how the base plate adjustment factors in.

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 all five required parameters depend on the description, and it only explains one of them ('Offer B base plate adjustment (cents)'). It never clarifies whether offerACents/offerBCents are lot totals or unit prices, or whether the quantities are units per lot — the single most consequential ambiguity for a price-comparison calculation.

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 states the verb and the broad resource ('Compare delivered prices ... using matching quantity units'), which is a recognizable unit-price comparison. But it never says it computes a per-unit price for offer A vs offer B and reports which is cheaper; the reader must assemble that from the parameter names. The trailing fragment 'Display stands' only restates the resource already in the name.

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 statement of when to use this versus the many sibling unit_price_* tools (binders, envelopes, etc.) or when not to use it. The only implicit guidance is the product category ('Display stands') plus 'in one currency', leaving the agent to infer that this is the display-stand variant of a shared comparison pattern.

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.