Skip to main content
Glama

The Doll Scout Home Tools

Calculate a break-even price · Selling craft supplies

tds_break_even_craft_stock
Read-onlyIdempotent

Find the lowest gross amount covering declared costs after fixed and proportional fees. Selling craft supplies. Declared order preparation charge (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>",
      "orderSortingChargesCents": "<orderSortingChargesCents>"
    },
    "name": "tds_break_even_craft_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixedFeeCentsYes
originalCostCentsYes
variableFeeBasisPointsYes
orderSortingChargesCentsYes

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 this is a read-only, idempotent, non-destructive, closed-world calculation. The description adds that the result is the lowest gross amount covering declared costs after fixed and proportional fees, but it does not explain rounding, fee stacking, or output units beyond the vague 'gross amount'.

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?

The opening sentence is front-loaded and purposeful, but the following fragments ('Selling craft supplies.' and 'Declared order preparation charge (cents).') read like orphaned metadata rather than integrated guidance.

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 with no parameter descriptions and no output schema, the definition leaves key semantics unexplained—especially originalCostCents, basis-point handling, and the return value's units. Annotations cover safety but not calculation completeness.

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 coverage is 0%, so the description must explain four required integer parameters. It alludes to fixed fees, proportional fees, and an order preparation charge, but never mentions originalCostCents and does not clarify variableFeeBasisPoints or how the values combine.

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 states a specific computation—finding the lowest gross amount that covers declared costs after fixed and proportional fees—and the title/description anchor it to selling craft supplies. This distinguishes the domain from other break-even siblings, though it does not explicitly name an alternative tool.

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 guidance on when to choose this craft-supply break-even calculator over the many sibling break-even tools, nor any prerequisites, exclusions, or conditions. The phrase 'Selling craft supplies' is the only contextual hint.

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.