Skip to main content
Glama

The Doll Scout Home Tools

Calculate a break-even price · Reselling a collector figure

tds_break_even_figure_resale
Read-onlyIdempotent

Find the lowest gross amount covering declared costs after fixed and proportional fees. Reselling a collector figure. New protective packing (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>",
      "protectivePackingCents": "<protectivePackingCents>"
    },
    "name": "tds_break_even_figure_resale"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixedFeeCentsYes
originalCostCentsYes
protectivePackingCentsYes
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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the key behavioral fact that the result is a gross amount that must cover costs plus both fee types, but it omits critical mechanics such as whether the proportional fee is computed on the gross or on cost, and 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 and the core operation is front-loaded, but the trailing fragments ('Reselling a collector figure. New protective packing (cents).') read as pasted labels rather than structured sentences. The '(cents)' note is ambiguous about which amounts it applies to.

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-required-parameter calculation tool with no output schema and no parameter documentation, the description should explain the formula and the unit/meaning of the result. It leaves the agent guessing about fee application and output format, which matters because the tool's sole purpose is producing a number.

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%, so the description must carry parameter meaning, and it only loosely maps 'declared costs' to originalCostCents, 'fixed and proportional fees' to fixedFeeCents/variableFeeBasisPoints, and 'protective packing' to protectivePackingCents. It never clarifies that basis points are a fraction of 10,000, nor the base to which the percentage applies, leaving the most consequential semantic undefined.

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 operation: find the lowest gross amount that covers declared costs after fixed and proportional fees. Combined with the title's domain ('Reselling a collector figure'), an agent can tell this is a break-even-price computation rather than a packing or pricing-label tool. It stops short of naming any sibling alternative, so it is clear but not differentiating.

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 when-to-use or when-not-to-use guidance; the only routing signal is the phrase 'Reselling a collector figure,' which implies the scenario rather than stating it. Nothing tells the agent how this differs from the many other tds_break_even_* variants.

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.