Skip to main content
Glama

The Doll Scout Home Tools

Compare unit offers · Art envelopes

tds_unit_price_art_envelopes
Read-onlyIdempotent

Compare delivered prices in one currency using matching quantity units and an explicit adjustment. Art envelopes. Offer B custom size (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>",
      "offerBCustomSizeCents": "<offerBCustomSizeCents>"
    },
    "name": "tds_unit_price_art_envelopes"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerACentsYes
offerBCentsYes
offerAQuantityYes
offerBQuantityYes
offerBCustomSizeCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description does add that the comparison happens in a single currency with matched quantity units and an 'explicit adjustment', but the adjustment is never explained, so the agent cannot tell how offerBCustomSizeCents actually affects the result. With annotations carrying the safety burden, a 3 is fair.

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?

It is short and front-loads the purpose, but it is written as three disconnected fragments, with 'Art envelopes.' and 'Offer B custom size (cents).' as sentence stubs. Every word is arguably load-bearing, but the telegraphic style makes the relationship between the sentences hard to parse.

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 computation tool with five required inputs, no output schema, and no schema descriptions, so the description is the only place the semantics can live. It omits what is returned (a unit price, a delta, a recommendation?) and how the B-side custom-size adjustment enters the calculation, which is the one thing an agent cannot infer.

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 compensate and largely does not. It clarifies that 'Offer B custom size (cents)' is an input, but the four other parameters (offerACents, offerAQuantity, offerBCents, offerBQuantity) are left to bare names, and the phrase 'explicit adjustment' gives no formula or sign convention for how the custom-size amount is applied.

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 first sentence gives a specific verb and resource ('Compare delivered prices') plus the normalization basis (one currency, matching quantity units), which is enough to tell it apart from the sibling tds_unit_price_* variants, whose difference is only the domain tag. The trailing 'Art envelopes' correctly identifies this variant's scope, but the description never says what the comparison actually returns, leaving the output form implicit.

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 choose this tool over the other tds_unit_price_* siblings, nor any prerequisite such as both offers needing the same currency or comparable quantities. The domain tag 'Art envelopes' is the only routing signal, and it is implied rather than explained.

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.