Skip to main content
Glama

The Doll Scout Home Tools

Compare unit offers · Corner protectors

tds_unit_price_corners
Read-onlyIdempotent

Compare delivered prices in one currency using matching quantity units and an explicit adjustment. Corner protectors. Offer B handling surcharge (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>",
      "offerBCornerSurchargeCents": "<offerBCornerSurchargeCents>"
    },
    "name": "tds_unit_price_corners"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerACentsYes
offerBCentsYes
offerAQuantityYes
offerBQuantityYes
offerBCornerSurchargeCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare the tool read-only, idempotent, non-destructive, and closed-world. The description adds useful context that prices are delivered prices compared in one currency, with matching quantity units and an explicit adjustment for Offer B's handling surcharge. It still does not explain the comparison formula, rounding behavior, or result format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the comparison purpose. The sentence fragments 'Corner protectors.' and 'Offer B handling surcharge (cents).' are terse, but they are not wasteful.

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 comparison tool with five required numeric inputs and no output schema, the description never states the comparison formula, rounding rules, or what the tool returns. The annotations cover the safety profile, but the description leaves too much undefined for correct 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 parameter meaning. It clarifies that the Offer B surcharge is in cents and hints that the two quantity fields should use matching units, but it does not individually define offerACents, offerBCents, offerAQuantity, or offerBQuantity, nor explain how the quantities relate to the prices.

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 verb and resource: 'Compare delivered prices' for 'Corner protectors.' The product-category phrase distinguishes it from sibling unit-price tools for other product types. However, 'explicit adjustment' is vague enough that the exact comparison purpose is not fully sharpened.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the product category 'Corner protectors,' which tells an agent when this category-specific comparison tool is relevant. There is no explicit when-to-use guidance, no exclusion, and no named alternative for comparing other product categories.

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.