Skip to main content
Glama

The Doll Scout Home Tools

Compare unit offers · Photo backdrop tiles

tds_unit_price_photo_backdrops
Read-onlyIdempotent

Compare delivered prices in one currency using matching quantity units and an explicit adjustment. Photo backdrop tiles. Offer B finish 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>",
      "offerBMatteFinishCents": "<offerBMatteFinishCents>"
    },
    "name": "tds_unit_price_photo_backdrops"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerACentsYes
offerBCentsYes
offerAQuantityYes
offerBQuantityYes
offerBMatteFinishCentsYes

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the single-currency constraint and the notion of an 'explicit adjustment', which is useful behavioral context. It stops short of explaining how the adjustment is applied or what the comparison returns, and with no output schema that matters.

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 verb, with no padding. But 'Photo backdrop tiles.' is a bare fragment and the terseness crosses into under-specification rather than economy — the space saved is spent nowhere useful.

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?

A five-parameter required-everything calculator with no output schema needs the description to explain the computation, the units, and the result shape. It supplies only the currency constraint and a one-word gloss on one parameter, leaving the adjustment mechanic and return value entirely undisclosed.

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% across five required parameters, so the description must carry the semantics and largely does not. 'Offer B finish adjustment (cents)' maps to offerBMatteFinishCents, but offerACents, offerBCents, offerAQuantity and offerBQuantity are left to inference — it is never clarified whether the finish cents are per unit or a one-time add-on, or that quantities are unit counts used to derive unit price.

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 gives a verb ('Compare') and a resource ('delivered prices'), and the fragment 'Photo backdrop tiles' differentiates this instance from the other tds_unit_price_* siblings. However, what the tool actually computes — unit price of offer A versus offer B with a finish surcharge applied — is never stated plainly, so an agent cannot confidently predict the operation from the description alone.

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?

'using matching quantity units' hints at a precondition (both quantities must be commensurable) but is not framed as a requirement. There is no when-to-use versus when-not guidance, no mention that the two offers must be in the same currency, and no reference to any alternative for single-offer price checks.

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.