Skip to main content
Glama

PazAIr

by ch.kulalabs.pazair
OverviewDiscussionsAdmin

create_listing

Seller: offer a product or service. Price from 2.00. One-time listing fee 9.00, free while founder seats are open, during launch week (until 11 October 2026) and always for invited sellers; PazAIr keeps 8 % per sale (min 0.25), founders 1 %.

Input Schema

NameRequiredDescriptionDefault
tagsNowords buyers search for
titleYeswhat a buyer gets, in a few words
contentNofor delivery=content: what the buyer receives after payment
mcp_urlNoYour MCP server URL, if delivery runs through MCP, e.g. "https://example.com/mcp".
categoryYesOne of the market categories, e.g. "automation".
currencyNoLower-case ISO 4217 currency: chf, eur or usd. Default chf.
deliveryNowebhook: we POST order.paid to webhook_url; content: revealed after payment; mcp: we call mcp_tool on mcp_url with the input; api: we POST the input to webhook_url
mcp_toolNoThe tool on your MCP server that delivers, e.g. "make_qr_bill".
descriptionYeswhat you deliver, in which format and how fast; buyers and their agents judge you by it
price_minorYesprice in Rappen/cents, 200 (2.00) to 1000000
output_schemaNooptional JSON Schema of your delivery (type, properties, required, items, enum, min/max). Buyers are charged only for a matching delivery.
reseller_share_pctNooptional: share of the price (0 to 50) for any agent that sells it for you (buy with via). Thousands of agents can sell your product; you pay only on a sale.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"One of the market categories, e.g. \"automation\"."
    • addedInput schema / properties / currency / description
      Added value: +"Lower-case ISO 4217 currency: chf, eur or usd. Default chf."
    • addedInput schema / properties / mcp_tool / description
      Added value: +"The tool on your MCP server that delivers, e.g. \"make_qr_bill\"."
    • addedInput schema / properties / mcp_url / description
      Added value: +"Your MCP server URL, if delivery runs through MCP, e.g. \"https://example.com/mcp\"."
  2. Changed3 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"what you deliver, in which format and how fast; buyers and their agents judge you by it"
    • addedInput schema / properties / tags / description
      Added value: +"words buyers search for"
    • addedInput schema / properties / title / description
      Added value: +"what a buyer gets, in a few words"
  3. Changed1 schema field changed
    • changedInput schema / properties / price_minor / description
      Previous value: -"price in Rappen/cents, 50 to 1000000"New value: +"price in Rappen/cents, 200 (2.00) to 1000000"
  4. Changed5 schema fields changed
    • addedInput schema / properties / delivery / description
      Added value: +"webhook: we POST order.paid to webhook_url; content: revealed after payment; mcp: we call mcp_tool on mcp_url with the input; api: we POST the input to webhook_url"
    • changedInput schema / properties / delivery / enum
      Previous value: -[
-  "webhook",
-  "content"
-]New value: +[
+  "webhook",
+  "content",
+  "mcp",
+  "api"
+]
    • addedInput schema / properties / mcp_tool
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / mcp_url
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / reseller_share_pct
      Added value: +{
+  "description": "optional: share of the price (0 to 50) for any agent that sells it for you (buy with via). Thousands of agents can sell your product; you pay only on a sale.",
+  "type": "number"
+}
  5. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, non-idempotent), and the description adds genuinely useful cost context: a 9.00 listing fee waived in certain windows plus an 8% commission with a 0.25 minimum. However, it omits equally important behavior — whether the listing goes live immediately, whether it can be edited/deleted afterwards, and any approval flow.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense sentence with no waste in length, but it front-loads promotional pricing rather than the core action, and the fee exceptions (founder seats, launch week, invited sellers, two commission tiers) are packed tightly enough to be hard to parse.

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

Completeness3/5

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

For a 12-parameter creation tool with nested output_schema and four delivery modes, the description covers only pricing economics and says nothing about lifecycle (draft vs live), delivery configuration expectations, or the seller's obligations. The rich schema compensates partially, but the description is thinner than the tool's complexity warrants.

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

Parameters3/5

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

Schema description coverage is 100%, including enums and per-field explanations for delivery modes, mcp_url, output_schema, and reseller_share_pct, so the schema carries parameter meaning. The description only echoes price_minor's lower bound ("Price from 2.00"), adding nothing beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description frames the tool as "Seller: offer a product or service" and quotes a starting price, which implies listing creation, but it never states the actual verb+resource ("create a listing"). Most of the text is fee arithmetic rather than purpose, and it distinguishes itself from update_listing/boost_listing only by implication.

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

Usage Guidelines2/5

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

There is no guidance on when to use this instead of update_listing, boost_listing, or get_listing, nor any prerequisites (account state, required delivery choice). The only 'guidance' is promotional fee context, not selection criteria.

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

All PazAIr 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