SoldStack

Buy or pass at a price

buy_or_pass

Read-onlyIdempotent

Whether an item is worth buying at a given cost to resell on Poshmark: buy, maybe or pass with the reason, judged from its clean sold comps after Poshmark's fee. Call it for one item at a time; if it reports busy, wait the given number of seconds and call again.

    query: brand + item, e.g. "patagonia better sweater".
    cost: what you'd pay, e.g. the thrift-store tag price, in the same currency as source (USD for poshmark, CAD for poshmark_ca).
    min_profit: smallest profit after fees worth the effort (default 10).
    size / condition: same filters as sold_comps.
    source: "poshmark" (US, default) or "poshmark_ca" (Poshmark Canada; prices and fees in CAD).

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": {
      "query": "<query>",
      "cost": "<cost>"
    },
    "name": "buy_or_pass"
  }
}

Input Schema

Name	Required	Default
`cost`	Yes
`size`	No
`query`	Yes
`source`	No	poshmark
`condition`	No
`min_profit`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026
- addedInput schema / properties / cost / maximum
```
Added value: +100000
```
- addedInput schema / properties / cost / minimum
```
Added value: +0
```
First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, so the description's job is to add context—and it does: the verdict is derived from clean sold comps after Poshmark's fee, and a busy signal requires a timed retry. It does not say how stale comps might be or what happens when no comps exist, which keeps it below a 5.

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 verdict sentence comes first, followed by operational guidance and then a compact per-parameter list; almost every line earns its place. It is slightly sprawling for a six-parameter tool, but not padded.

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

Completeness5/5

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

For a six-parameter tool with no schema descriptions and no output schema, the definition still covers the return values (buy/maybe/pass with reason), fee-adjusted judgment logic, currency behavior per source, budget default, and retry handling—enough to call it correctly without further context.

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 coverage is 0%, so the description carries the full burden and mostly meets it: query format is exemplified, cost is explained with currency tied to source, min_profit is given a default and meaning, and size/condition are delegated to sold_comps. The accepted condition values and the cost upper bound are left unstated.

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 opens with a specific verb+resource: decide whether an item is worth buying at a given cost for Poshmark resale, returning buy/maybe/pass plus a reason. That is clearly distinct from the sibling sold_comps, which supplies the underlying comps rather than a verdict.

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

Usage Guidelines4/5

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

"Call it for one item at a time; if it reports busy, wait the given number of seconds and call again" gives concrete usage and retry guidance. The relationship to sold_comps is implied via shared size/condition filters, but there is no explicit statement of when to prefer this tool over raw comps.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SoldStack tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?