Skip to main content
Glama

The Doll Scout Home Tools

Calculate a break-even price · Reselling a tote online

tds_break_even_online_tote
Read-onlyIdempotent

Find the lowest gross amount covering declared costs after fixed and proportional fees. Reselling a tote online. Seller-paid carrier costs (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>",
      "sellerCarrierCents": "<sellerCarrierCents>"
    },
    "name": "tds_break_even_online_tote"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixedFeeCentsYes
originalCostCentsYes
sellerCarrierCentsYes
variableFeeBasisPointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavior context by specifying the arithmetic model — fixed plus proportional fees applied to declared costs, with seller-paid carrier costs — but says nothing about what the returned amount includes or excludes (e.g., whether carrier cost enters the gross or the cost base).

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 front-loads the core definition, but the trailing fragments ("Reselling a tote online.", "Seller-paid carrier costs (cents).") read as disconnected labels rather than a structured sentence. Nothing is wasted, but the fragments are under-specified rather than concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter pure computation with no output schema, the definition covers the formula intent and the unit convention, and the annotations cover safety. The remaining gap is the return value's composition and units, which the description only gestures at with "lowest gross amount".

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% across four required parameters, so the description carries the full burden. It maps "fixed fees", "proportional fees" and "seller-paid carrier costs (cents)" loosely onto three fields, but leaves originalCostCents as the vague "declared costs" and never explains that variableFeeBasisPoints is a basis-point (1/100 percent) value, which is the most error-prone input.

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?

"Find the lowest gross amount covering declared costs after fixed and proportional fees" states a specific computation and its inputs, and "Reselling a tote online" fixes the scenario, which is enough to distinguish this from the many tds_break_even_* siblings. It stops short of naming a sibling or stating how the tote variant differs, so it is clear but not fully differentiated.

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?

"Reselling a tote online" implies a scenario but gives no explicit when-to-use rule, no prerequisites, and no statement about when to pick another break-even tool (art print, card lot, etc.) instead. The agent must infer selection from the scenario fragment 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.