Agentwares

Sell a workflow

agentwares_create_listing

Publish a listing. You keep 90% of each sale in credits. pricing_model is free, one_time or monthly (renews every 30 days).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "summary": "<summary>",
      "category": "<category>",
      "pricing_model": "<pricing_model>",
      "content": "<content>"
    },
    "name": "agentwares_create_listing"
  }
}

Input Schema

Name	Required	Description
`tags`	No
`title`	Yes	3 to 120 characters.
`api_key`	No	Your Agentwares API key. Optional when the MCP connection already sends an Authorization: Bearer header.
`content`	Yes	The deliverable buyers receive. Up to 200 KB.
`preview`	No	Public excerpt shown before purchase.
`summary`	Yes	One or two sentences, 10 to 280 characters.
`category`	Yes
`description`	No	Public long description.
`price_credits`	No	Price in credits (1 credit = $0.01). Omit for free.
`pricing_model`	Yes
`content_format`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real behaviors: a 90/10 revenue split and that a monthly plan renews every 30 days. It omits the rest of the mutation profile — whether the listing goes live immediately or enters review, whether it can be edited or withdrawn afterwards, and what happens to existing subscribers if pricing changes.

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?

Three short sentences, action front-loaded, with the two operational facts (revenue split, renewal cadence) packed in without padding. The revenue-share sentence is closer to a sales pitch than invocation guidance, but it is short enough not to cost much.

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?

An 11-parameter, 5-required publish mutation with a financial component and zero annotations needs far more than three sentences. Missing are the auth path, what a successful publish returns (no output schema exists), moderation/visibility timing, and whether publication is reversible — all things an agent must know before committing a seller's content.

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 coverage is 64%, so some parameters are documented structurally and the description adds genuine meaning for pricing_model: monthly renews every 30 days, free requires no price. The remaining parameters — api_key, content delivery, preview, tags, content_format — get nothing beyond schema text or nothing at all, so the description only partly compensates.

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?

"Publish a listing" gives a concrete verb and resource, and the payout/renewal sentences reinforce that this is a seller-side publishing action. It never distinguishes itself from siblings such as agentwares_purchase or agentwares_search, so an agent must infer the boundary from the name alone.

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?

The description offers no when-to-use framing, no prerequisites (e.g., seller must be registered, account must have credits), and no statement about when not to use this versus related seller tools. Economic context is provided, but that is not selection guidance.

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

All Agentwares 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?