Skip to main content
Glama

The Doll Scout Home Tools

Calculate a break-even price · Selling a set at a market

tds_break_even_market_set
Read-onlyIdempotent

Find the lowest gross amount covering declared costs after fixed and proportional fees. Selling a set at a market. Allocated part of the booth fee (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>",
      "allocatedBoothCents": "<allocatedBoothCents>"
    },
    "name": "tds_break_even_market_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixedFeeCentsYes
originalCostCentsYes
allocatedBoothCentsYes
variableFeeBasisPointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 and the description is not obligated to restate it. The description adds genuine behavioral context by describing the calculation model (costs plus fixed and proportional fees). It does not disclose the return value, rounding behavior, or whether the proportional fee is applied to the gross amount — the detail that actually determines the break-even solve.

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 core computation is front-loaded in the first sentence, which is good, but the two trailing fragments are under-specified rather than concise and interrupt the flow. The final sentence duplicates the parameter name allocatedBoothCents almost verbatim without adding meaning. The text is short, but not all of it earns its place.

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 pure calculation tool with four required numeric parameters at 0% schema coverage and no output schema. The description does not say what the tool returns (presumably a price in cents), whether results are rounded, or how the proportional fee interacts with the solved gross amount. For a deterministic function where the caller must interpret the number, that omission leaves a real gap.

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% across four required parameters, so the description must carry the load. It does loosely map all four: 'declared costs' to originalCostCents, 'fixed and proportional fees' to fixedFeeCents and variableFeeBasisPoints, and 'allocated part of the booth fee (cents)' to allocatedBoothCents. It never states units for the basis-points parameter or the fee-on-gross relationship, so the mapping is suggestive rather than precise.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a concrete computation — the lowest gross amount that covers declared costs after fixed and proportional fees — which is more than a restatement of the name. However, the following two sentences ('Selling a set at a market. Allocated part of the booth fee (cents).') are fragments that read like a scenario tag and a parameter gloss, so the purpose is only partially resolved. Nothing in the text differentiates this from the many sibling tds_break_even_* variants beyond the scenario label.

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, no exclusion of alternative tools, and no stated prerequisites. The phrase 'Selling a set at a market' weakly implies a scenario, but the agent must infer from the name alone whether this or a sibling break-even tool applies. No mention of what to do if the result is negative or how it relates to the price-label tools.

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.