Skip to main content
Glama

The Doll Scout Home Tools

Compare unit offers · Display mounting strips

tds_unit_price_mount_strips
Read-onlyIdempotent

Compare delivered prices in one currency using matching quantity units and an explicit adjustment. Display mounting strips. Offer B surface preparation (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>",
      "offerBSurfacePrepCents": "<offerBSurfacePrepCents>"
    },
    "name": "tds_unit_price_mount_strips"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerACentsYes
offerBCentsYes
offerAQuantityYes
offerBQuantityYes
offerBSurfacePrepCentsYes

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, closed-world, non-destructive, so the safety profile is covered. The description adds that comparison happens in a single currency, that quantities must share units, and that offer B carries a surface-prep adjustment in cents — useful context, but it never states whether the adjustment is applied per unit or to the total, which is the decisive behavioral detail for a calculation tool.

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?

Only three short sentences, and the core comparison statement is front-loaded. The middle sentence is a bare product label and the third is a terse fragment, so the text is short but not cleanly structured as an explanation.

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 five-parameter computation with no output schema and no parameter descriptions, the definition leaves the central arithmetic undefined: how the surface-prep adjustment enters the comparison and what the result represents. An agent could invoke it, but not confidently predict the outcome.

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 meaning. It only clarifies offerBSurfacePrepCents (cents, offer B) and hints that quantities must match units; it does not say whether offerACents/offerBCents are lot totals to be divided by quantity or already-unit prices, nor what currency 'cents' refers to.

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 opening clause gives a verb and resource ('Compare delivered prices ... using matching quantity units'), and the product line 'Display mounting strips' separates it from the many tds_unit_price_* siblings covering stands, binders, envelopes, etc. However, 'an explicit adjustment' is cryptic and the fragment 'Display mounting strips.' reads as a dangling label rather than a stated purpose, so an agent cannot fully tell what value is computed.

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 tool versus the sibling price tools, no prerequisites, and no exclusions. The only routing signal is the product noun, which the agent must infer is the selection criterion.

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.