Skip to main content
Glama

Worth buying at this cost?

worth_it
Read-onlyIdempotent

What the seller keeps after eBay fees and a verdict (worth it / thin / pass) for an expected sale price and what the user would pay. Pure arithmetic in the currency you give it, with eBay US fees: pass the sale price and the cost in the same currency (the one price_item named in price.currency). For a seller on eBay UK, the worthIt block price_item returns already uses their own fees. Use price_item first when the sale price is unknown.

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": {
      "expected_sale_price": "<expected_sale_price>",
      "cost": "<cost>"
    },
    "name": "worth_it"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYesWhat the user would pay for the item, in the same currency as expected_sale_price.
expected_sale_priceYesExpected eBay sale price, in the same currency as cost.

Output Schema

NameRequiredDescriptionDefault
costNo
ruleNo
textNo
labelNoThe verdict in words.
profitNo
verdictNo
unstructuredNoTrue: read `text`.
netAfterEbayFeesNoWhat the seller keeps after eBay fees.
expectedSalePriceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "cost": {
      +      "type": "number"
      +    },
      +    "expectedSalePrice": {
      +      "type": "number"
      +    },
      +    "label": {
      +      "description": "The verdict in words.",
      +      "type": "string"
      +    },
      +    "netAfterEbayFees": {
      +      "description": "What the seller keeps after eBay fees.",
      +      "type": "number"
      +    },
      +    "profit": {
      +      "type": "number"
      +    },
      +    "rule": {
      +      "type": "string"
      +    },
      +    "text": {
      +      "type": "string"
      +    },
      +    "unstructured": {
      +      "description": "True: read `text`.",
      +      "type": "boolean"
      +    },
      +    "verdict": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / cost / description
      Previous value: -"What the user would pay for the item in USD."New value: +"What the user would pay for the item, in the same currency as expected_sale_price."
    • changedInput schema / properties / expected_sale_price / description
      Previous value: -"Expected eBay sale price in USD."New value: +"Expected eBay sale price, in the same currency as cost."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds the fee model used (eBay US), the currency assumption, and the categorical outcome space. It stops short of quantifying the verdict thresholds, which is the one behavioral detail an agent might still want.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The outcome and inputs are front-loaded in the first clause, then constraints follow. It is dense but mostly earns its words; the nested parentheticals make it slightly harder to parse than necessary.

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?

With an output schema present, the description needn't explain return values, and it still names the verdict categories. Currency handling, fee region, and the price_item prerequisite are all covered, leaving only the verdict thresholds unspecified.

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 100%, so both parameters are already documented, giving a baseline of 3. The description adds modest meaning by tying the currency to the one price_item reported in price.currency rather than leaving it free-form, but it adds no units or bounds beyond the schema.

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

Purpose5/5

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

The description names the specific computation (what the seller keeps after eBay fees) plus the verdict output (worth it / thin / pass) from two named inputs. It also distinguishes itself from price_item, making it identifiable without opening any schema.

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

Usage Guidelines5/5

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

Explicit routing guidance: 'Use price_item first when the sale price is unknown,' and a named alternative for UK sellers ('the worthIt block price_item returns already uses their own fees'). It also states the preconditions on currency matching.

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.

Resources