Skip to main content
Glama

agent-ready-kit

by com.mudko

Create Bazaar Listing (engagement customers)

create_bazaar_listing

Use this when a PAID engagement customer (valid bundle_key) wants their x402 endpoint listed in Coinbase's x402 Bazaar — the package is INCLUDED free with any engagement. Provisions the listing and returns a listing_key that drives the automated pipeline (get_bazaar_listing_kit → deploy → check_bazaar_listing). Buyers WITHOUT a bundle_key purchase the standalone $99 Bazaar Listing Package instead: agent wallets pay https://mudko.com/api/x402/bazaar-listing (x402, USDC on Base); humans ask at /talk for a card link. Details (resource_url, pay_to, price_usd, stack) are optional here — the kit tool collects whatever is missing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesCustomer email — the listing_key is bound to it (required).
stackNoServer stack — picks the generated kit variant (optional).
pay_toNoReceiving wallet (0x… on Base) the endpoint pays to (optional).
price_usdNoEndpoint price per call in USD (optional).
bundle_keyYesEngagement bundle key (required — this tool is the engagement freebie).
resource_urlNoHTTPS URL of the endpoint to list (optional).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
listingNoListing summary incl. listing_key and state.
messageNo
next_stepNoThe exact next call to make — the pipeline is resumable from any agent session.

TDQS

A4.6/5.0
Behavior4/5

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

Adds behavioral context beyond annotations: provisions listing, returns listing_key, drives pipeline, notes that optional params are collected by kit tool. No contradiction with annotations.

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?

Well-structured and front-loaded with core purpose. Slightly long but each sentence earns its place by providing clear guidance.

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

Completeness5/5

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

Given complexity (6 params, 2 required, output schema exists) and sibling tools, description covers process flow, distinguishes customer types, and references pipeline sequence completely.

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 100% so baseline 3. Description adds meaning: bundle_key is engagement freebie, email binds listing_key, optional params are handled by kit tool. Does not repeat schema.

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 clearly states the tool creates a bazaar listing for paid engagement customers with a valid bundle_key. It distinguishes from the standalone purchase path and outlines the pipeline.

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

Usage Guidelines5/5

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

Explicitly states when to use (paid engagement customer with bundle_key) and when not (buyers without bundle_key use standalone purchase). Provides alternative URL for the standalone path.

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

All agent-ready-kit toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose, with descriptions that prevent confusion. Tools like scan_site and run_site_audit are differentiated by their focus on AI-readiness vs. site quality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case, with clear action words like 'scan', 'create', 'get', 'verify'. Even longer names like 'summarize_scan_for_humans' maintain consistency.

Tool Count4/5

22 tools is slightly above the ideal range but justified by the comprehensive scope of the server, covering scanning, analysis, quoting, file delivery, and verification. Some tools like generate_files and get_customer_files could overlap but serve different contexts.

Completeness5/5

The tool surface covers the entire workflow from site scanning to deployment verification, with no obvious dead ends. All necessary operations for making a site agent-ready are present, including edge cases like x402 validation and credential verification.

Resources