Skip to main content
Glama

The Doll Scout Home Tools

Compare unit offers · Storage crates

tds_unit_price_storage_crates
Read-onlyIdempotent

Compare delivered prices in one currency using matching quantity units and an explicit adjustment. Storage crates. Offer B matching lids (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>",
      "offerBExtraLidCents": "<offerBExtraLidCents>"
    },
    "name": "tds_unit_price_storage_crates"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerACentsYes
offerBCentsYes
offerAQuantityYes
offerBQuantityYes
offerBExtraLidCentsYes

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?

Annotations already cover the read-only, idempotent, non-destructive safety profile. The description adds useful constraints — one currency, matching quantity units, and an explicit adjustment for Offer B matching lids — but does not explain the comparison output or how the adjustment is applied. It adds some value beyond annotations but leaves key behavioral gaps.

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 very short and front-loads the main operation. The fragment style ('Storage crates.' / 'Offer B matching lids (cents).') is efficient but slightly choppy, keeping it from a 5.

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?

This is a read-only comparison tool with five required parameters and no output schema, yet the description does not explain what the comparison returns or how to interpret the result. It also lacks usage guidance, leaving the agent under-informed for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 parameter meaning. It implies cents for prices, quantities for the quantity fields, and that offerBExtraLidCents represents matching lid costs, but it does not clearly define each of the five parameters or explain how offerA and offerB are structured. It adds partial meaning but does not fully compensate for the schema gap.

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 uses a specific verb ('Compare') and resource ('delivered prices'), and names the product domain ('Storage crates'), which distinguishes it from sibling category variants. It does not explicitly state that it computes unit prices, so it stops short of a 5.

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?

The description gives no when-to-use guidance, no exclusions, and no mention of alternative tools. Usage is only implied by the product name and operation, leaving the agent to infer 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.