drop_get
Read one of the caller's own drops by id: name, symbol, description, the brand kit it renders with, the image, the exact USD price an edition costs, the payout address, whether it is `draft` or `live`, the supply, and the public mint page path. Free, and it reads the caller's records only. A drop owned by another creator is answered with the same not-found as one that does not exist — the store filters by owner inside its query, so there is nothing here to probe with. Read a drop before `drop_update` it, and before telling a user what a drop is: `priceUsd` is an exact decimal string rather than a float, `supply` is `{ total, minted, remaining }`, and a `draft` is not collectable. This tool does not mint, does not publish, and does not charge anything.
Read one of the caller's own drops by id: name, symbol, description, the brand kit it renders with, the image, the exact USD price an edition costs, the payout address, whether it is draft or live, the supply, and the public mint page path. Free, and it reads the caller's records only. A drop owned by another creator is answered with the same not-found as one that does not exist — the store filters by owner inside its query, so there is nothing here to probe with. Read a drop before drop_update it, and before telling a user what a drop is: priceUsd is an exact decimal string rather than a float, supply is { total, minted, remaining }, and a draft is not collectable. This tool does not mint, does not publish, and does not charge anything.
Input
The tool takes a single JSON object. Every field, its type, and an example are on the generated reference at GET /mcp/tools, under this tool's name.
Calling it
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": { "name": "drop_get", "arguments": {} }
}Put your arguments in place of the empty object. A call that fails comes back as a normal result carrying isError: true and a message naming what went wrong, not as a JSON-RPC protocol error.
Notes
The category is Creator, subcategory Drops. The full request and response shape, and a live playground, live on the generated reference at GET /mcp/tools.
drop_list
List the drops the authenticated caller owns, newest first: name, symbol, description, the brand kit it renders with, the image, the exact USD price an edition costs, the payout address, whether it is `draft` or `live`, the supply, and the public mint page path. Takes no arguments, costs nothing, and reads the caller's own records only. Call it before `drop_get`, `drop_update`, or `drop_create` — a drop is scoped to its owner, and a drop that belongs to someone else reads the same as one that does not exist, so this list is the only place an id can honestly come from. `supply` is `{ total, minted, remaining }`; `priceUsd` is an exact decimal string, never a float, so a price at the top of the range is not silently rounded. `mintPageUrl` is a path on the api origin, not an absolute link — resolve it against the host you are talking to. This tool does not mint, publish, or charge anything.
drop_create
Create a drop for the authenticated caller: a named, fixed-supply edition at an exact USD price, rendered with one of the caller's own brand kits. Free — it costs no credits, takes no signature, moves no money, and mints nothing. The new drop is a `draft`, and a draft's mint page answers 404: publishing it is a separate, irreversible step (`status: "live"`) that this tool and `drop_update` both deliberately do NOT expose, because it is a `publish` approval in putty's model and a direct tool call has no run to ask through. Take the created drop to the person, who publishes it through the real path. Two rules are refused rather than defaulted, and both are the mistakes that are invisible until a collector's money goes somewhere the creator cannot see: a `brandKitId` that is not a kit YOU own (answered the same as one that does not exist, so this is not an id oracle), and a `priceUsd` above zero with no `creatorAddress` — putty never holds a creator's takings and has no address to fall back on. Every problem with the drop is reported at once, as sentences, so a creator fixing one field per round trip is not forced into three. `supply` is fixed at creation and never changes, because every sold edition's buyer was promised a collection of a given size; at most 10,000.