Skip to main content
Glama

The Doll Scout Home Tools

Calculate a break-even price · Selling a card lot

tds_break_even_card_lot
Read-onlyIdempotent

Find the lowest gross amount covering declared costs after fixed and proportional fees. Selling a card lot. Materials used for sorting (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>",
      "sortingSupplyCents": "<sortingSupplyCents>"
    },
    "name": "tds_break_even_card_lot"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixedFeeCentsYes
originalCostCentsYes
sortingSupplyCentsYes
variableFeeBasisPointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 covered. The description adds the actual computation logic (fixed plus proportional fees netted out of costs), which is genuine value, but it never states what the result looks like — notably whether the returned break-even price is in cents.

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 sentence is front-loaded and earns its place, but the trailing noun fragments ('Selling a card lot. Materials used for sorting (cents).') read as clipped notes rather than structured guidance and cost clarity for only a few words saved.

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

Completeness3/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, the definition should say what is returned and in what unit. It describes the inputs' roles adequately but leaves the return value entirely unspecified, which is the main remaining gap for an agent deciding how to consume the result.

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

Parameters4/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 largely does: 'declared costs' maps to originalCostCents, 'fixed and proportional fees' maps to fixedFeeCents and variableFeeBasisPoints, and 'Materials used for sorting (cents)' maps to sortingSupplyCents with an explicit unit. It stops short of clarifying that variableFeeBasisPoints is in basis points (1/100 of a percent), leaving one non-obvious unit unexplained.

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?

States a specific operation: finding the lowest gross amount that covers declared costs after fixed and proportional fees. The added fragment 'Selling a card lot' scopes it to a particular resale scenario, which distinguishes it from the many sibling break-even variants (art print, consignment frame, craft stock) without naming them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the scenario tag 'Selling a card lot'; there is no explicit statement of when to call this versus the sibling break-even tools, nor any prerequisite or exclusion. An agent can infer the context but must guess at boundaries.

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.