Skip to main content
Glama

SoldStack

by dev.soldstack
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 USD.
    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

TableJSON Schema
NameRequiredDescriptionDefault
costYes
sizeNo
queryYes
sourceNoposhmark
conditionNo
min_profitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, but the description adds genuinely new behavior: a concurrency/busy lock with a retry-after delay, the fee deduction applied before judging, and region-dependent currency and fee treatment (USD vs CAD). That is meaningful context beyond the annotation block.

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 its basis are front-loaded in the first sentence, followed by a compact parameter line-list, each entry earning its place with an example or default. Slightly long but no filler.

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 no output schema, the description does communicate the result shape (a decision plus reason) and covers retry behavior, fee handling, and regional variants. It is comfortably complete for a two-required-parameter decision tool, with only the size/condition filter semantics left to the sibling tool.

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 it defines query format with an example, explains cost as the acquisition price in USD, gives min_profit's default and meaning, and enumerates source values with their currency implications. Only size/condition are left unexplained beyond a pointer to sold_comps.

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 states a specific decision outcome (buy, maybe, pass with reason) judged from sold comps after Poshmark's fee, which is far more than a restatement of the name. It also distinguishes itself from the sibling sold_comps by tying its size/condition filters to that tool rather than duplicating them.

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 concrete operational guidance: call for one item at a time, and if it reports busy, wait the stated seconds and retry. It also implicitly positions sold_comps as the raw-data counterpart via 'same filters as sold_comps', but never states explicitly when to prefer this tool over sold_comps.

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