agentic-commerce

create_seller

Destructive

Creates a seller account on Boson Protocol. Required before creating any offers. signerAddress is automatically set as admin, assistant, and treasury. Provide seller metadata and royaltyPercentage. Returns unsigned transaction data.

Input Schema

Name	Required	Description
`kind`	Yes
`name`	No
`type`	Yes
`images`	No
`website`	No
`configId`	Yes	Boson/Fermion Protocol deployment identifier. Format: '<env>-<chainId>-<index>' e.g. 'production-137-0' (Polygon mainnet), 'testing-80002-0' (Amoy testnet). Call get_config_ids to list all valid values for this server.
`authTokenId`	Yes	NFT token ID used as auth token (e.g. Lens profile ID). Pass '0' if not using auth tokens.
`contractUri`	No	Optional URI for OpenSea-style storefront metadata (defaults to empty string, meaning none). When set, it is fetched to copy it to The Graph's IPFS node, so it must be an ipfs:// URI, a CID, or an http(s) URL returning JSON.
`description`	No
`socialLinks`	No
`contactLinks`	No
`authTokenType`	Yes	Auth token type: 0=None, 1=Lens Protocol profile NFT.
`executionMode`	No	'direct' = standard on-chain tx (sign locally with your wallet → send_signed_transaction). 'metaTx' = gasless relay via Biconomy (send_meta_transaction). Defaults to 'direct'.
`salesChannels`	No
`signerAddress`	Yes	Ethereum address that will sign and send this transaction. Must match the wallet that will sign the returned transaction locally.
`legalTradingName`	No
`contactPreference`	Yes
`royaltyPercentage`	Yes	Default resale royalty in basis points (0–10000). Applied to all offers unless overridden.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / contractUri / default
```
Added value: +""
```

changedInput schema / properties / contractUri / description

Previous value: -"URI for OpenSea-style storefront metadata. Can be IPFS URI or empty string."New value: +"Optional URI for OpenSea-style storefront metadata (defaults to empty string, meaning none). When set, it is fetched to copy it to The Graph's IPFS node, so it must be an ipfs:// URI, a CID, or an http(s) URL returning JSON."

changedInput schema / required

Previous value: -[
-  "type",
-  "kind",
-  "contactPreference",
-  "contractUri",
-  "royaltyPercentage",
-  "authTokenId",
-  "authTokenType",
-  "configId",
-  "signerAddress"
-]New value: +[
+  "type",
+  "kind",
+  "contactPreference",
+  "royaltyPercentage",
+  "authTokenId",
+  "authTokenType",
+  "configId",
+  "signerAddress"
+]

First observedJul 15, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond the destructiveHint=true/write annotations, the description discloses two non-obvious behaviors: signerAddress is auto-assigned as admin/assistant/treasury, and the tool returns unsigned transaction data rather than executing on-chain. This tells the agent a follow-up sign/send step is required. It does not flag irreversibility of the on-chain account creation.

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?

Four short sentences, front-loaded with the purpose, then prerequisite, behavior, and inputs. Generally efficient, though "Provide seller metadata and royaltyPercentage" adds little beyond what the schema already conveys.

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

Completeness2/5

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

For an 18-parameter creation tool with no output schema and low schema coverage, the description covers the transaction-return behavior but omits guidance on many required structural parameters. An agent would still rely heavily on the schema and guesswork for fields like type and kind.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 39% across 18 parameters. The description only re-mentions royaltyPercentage and signerAddress (already documented in the schema) and vaguely says "Provide seller metadata," leaving required params like type, kind, contactPreference, authTokenId, and authTokenType unexplained in both places. It fails to compensate for the coverage gap.

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?

States a specific verb and resource ("Creates a seller account on Boson Protocol") and frames its role as a prerequisite for offers. It is clearly distinguishable from create_buyer and create_offer, though it does not explicitly contrast with update_seller, which would have earned a 5.

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?

"Required before creating any offers" provides clear, actionable context for when this tool is needed. It stops short of naming exclusions or the alternative (update_seller for existing accounts), so it does not reach a 5.

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

All agentic-commerce 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?