Skip to main content
Glama
Sign In

SoldStack

by io.github.aar-ont
OverviewDiscussionsAdmin

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).

Input Schema

NameRequiredDescriptionDefault
costYes
sizeNo
queryYes
sourceNoposhmark
conditionNo
min_profitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / source
      Added value: +{
+  "default": "poshmark",
+  "title": "Source",
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantive context beyond them: output is a buy/maybe/pass verdict with a reason, comps are fee-adjusted, currency follows the source (USD vs CAD), and there is documented rate-limit retry behavior.

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 definition is front-loaded, followed by operational notes, then a compact per-parameter list. Nearly every line earns its place; only minor formatting artifacts and the deferred size/condition line dilute it.

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 six-parameter tool with no output schema, the description covers the return shape (verdict plus reason), the fee/currency model, retry behavior, and all parameters. It omits how comps are selected (lookback window, comp count), which limits full confidence in the verdict.

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?

With 0% schema description coverage the description carries the burden and mostly does: query format is exemplified, cost is explained against the source currency, min_profit gets a default and meaning, and source values are enumerated with currency implications. Only size/condition are deferred to 'same filters as sold_comps' without format detail.

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 description states exactly what the tool produces: a buy/maybe/pass verdict with a reason, derived from sold comps net of Poshmark fees. It is distinguishable from sold_comps by output type (a decision, not raw comps), though it never explicitly names sold_comps as the alternative for raw data.

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?

It gives clear operating context — evaluate one item at a time, and on a 'busy' response wait and retry — plus the implicit condition of use (you have a cost and want a resale verdict). It stops short of explicit when-not guidance or routing to siblings.

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

All SoldStack toolsInspect
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