Skip to main content
Glama

The Doll Scout Home Tools

Calculate a break-even price · Selling a used shelf

tds_break_even_used_shelf
Read-onlyIdempotent

Find the lowest gross amount covering declared costs after fixed and proportional fees. Selling a used shelf. Your delivery expense (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": {
      "originalCostCents": "<originalCostCents>",
      "fixedFeeCents": "<fixedFeeCents>",
      "variableFeeBasisPoints": "<variableFeeBasisPoints>",
      "bufferDeliveryCents": "<bufferDeliveryCents>"
    },
    "name": "tds_break_even_used_shelf"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixedFeeCentsYes
originalCostCentsYes
bufferDeliveryCentsYes
variableFeeBasisPointsYes

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the meaningful behavioral fact that the result is a fee-adjusted break-even gross amount, but says nothing about rounding, fee application order, or what the returned value looks like.

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 with no filler, but the structure is three disconnected fragments ('...fees. Selling a used shelf. Your delivery expense (cents).') that read as tacked-on labels rather than a coherent spec. Front-loading the computation is good; the trailing fragments add ambiguity rather than clarity.

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 four-parameter calculation tool with no output schema and zero schema coverage, the description is under-specified: an agent cannot tell what units or semantics the fee parameters carry or what exactly is returned. Annotations cover the read-only nature, but the computational contract is largely missing.

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% for all four required parameters, so the description must carry the burden. It only vaguely gestures at one input with 'Your delivery expense (cents)' (presumably bufferDeliveryCents) and never explains originalCostCents, fixedFeeCents, or variableFeeBasisPoints, leaving three parameters undocumented in both places.

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 names a specific computation: the lowest gross amount that covers declared costs after fixed and proportional fees, and 'Selling a used shelf' pins the scenario, distinguishing it from the many sibling break-even tools for binders, prints, card lots, etc. It is not a tautology of the name, though it never uses the word 'break-even price' directly as the output.

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 explicit statement of when to use this versus the sibling break-even calculators or versus price-label tools like tds_shelf_price_label. The item-type phrase 'Selling a used shelf' implies the scenario but leaves the agent to infer selection criteria and prerequisites entirely.

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.