Skip to main content
Glama

The Doll Scout Home Tools

Calculate a break-even price · Selling a used photo stand

tds_break_even_photo_stand
Read-onlyIdempotent

Find the lowest gross amount covering declared costs after fixed and proportional fees. Selling a used photo stand. Packing for the tubes (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>",
      "anodizedTubeWrapCents": "<anodizedTubeWrapCents>"
    },
    "name": "tds_break_even_photo_stand"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixedFeeCentsYes
originalCostCentsYes
anodizedTubeWrapCentsYes
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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description adds the computational intent (lowest gross amount covering costs plus fixed and proportional fees), but says nothing about rounding, result sign, or fee application order beyond that.

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?

Very short, but built from sentence fragments that are not front-loaded around the core action; 'Packing for the tubes (cents)' is unclear rather than economical. Length is fine, but the structure obscures rather than clarifies.

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?

With four required parameters at 0% schema coverage and no output schema, the description must carry both input meaning and the expected result, yet it never states what is returned (presumably a break-even price in cents) or how the anodized tube wrap cost enters the calculation. It is under-specified for a calculation tool with no other documentation.

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 give meaning to four cryptic required parameters, yet it only gestures at fees ('fixed and proportional') and alludes to one parameter with the opaque fragment 'Packing for the tubes (cents)'. originalCostCents and the basis-points unit of variableFeeBasisPoints remain 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?

The first sentence gives a specific verb and resource: find the lowest gross amount covering declared costs after fixed and proportional fees. The following fragments ("Selling a used photo stand. Packing for the tubes (cents).") tie it to the specific item variant, which is how the numerous tds_break_even_* siblings differ, but they read as notes rather than a coherent statement of purpose.

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 guidance on when to use this tool versus a sibling such as tds_break_even_market_set or tds_unit_price_display_stands, and no stated preconditions. Usage is only implied by the item-specific fragments.

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.