Skip to main content
Glama

The Doll Scout Home Tools

Calculate a break-even price · Selling an art print

tds_break_even_art_print
Read-onlyIdempotent

Find the lowest gross amount covering declared costs after fixed and proportional fees. Selling an art print. Handling and packing supplies (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>",
      "printHandlingCents": "<printHandlingCents>"
    },
    "name": "tds_break_even_art_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixedFeeCentsYes
originalCostCentsYes
printHandlingCentsYes
variableFeeBasisPointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds the meaningful behavioral fact that the answer is the minimum gross amount covering costs after both fixed and proportional fees, which tells the agent what the computation optimizes for. It stops short of describing fee application order, rounding, or what the returned value looks like, which is the main remaining gap.

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?

At three short sentences the size is appropriate and the core definition is front-loaded. The trailing fragments "Selling an art print. Handling and packing supplies (cents)." are telegraphic and read as disconnected labels rather than structured guidance, so the text is compact but not well organized.

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 four-parameter arithmetic tool with 0% schema description coverage and no output schema, so the description carries a heavy burden and does not meet it. It never states the formula, whether the result is in cents or currency units, or how the basis-point fee is converted, leaving the agent unable to interpret the return value confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 compensate, and it partially does: "declared costs" maps to originalCostCents, "fixed ... fees" to fixedFeeCents, "proportional fees" to variableFeeBasisPoints, and "Handling and packing supplies (cents)" to printHandlingCents. However, it never explains that the fee parameter is expressed in basis points, nor how the proportional fee is applied to the cost base, so the agent still has to guess at semantics the schema does not supply.

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: find the lowest gross amount that covers declared costs after fixed and proportional fees. That is a clear verb+resource and, combined with the title and "Selling an art print" scenario tag, separates it from the sibling break-even variants for cards, consignment frames, and other categories. The phrasing "lowest gross amount" is slightly abstract rather than saying "break-even price," which keeps it from a 5.

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 guidance and no exclusion of alternatives; the only routing signal is the fragment "Selling an art print," which implies a product scenario but never says to prefer this over tds_break_even_card_lot or similar siblings. An agent must infer the selection rule from the tool name alone.

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.