Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

marketplace_submit

Submits an agent endpoint to the AgentPayStore marketplace for review, requiring a live x402 USDC payment envelope, and returns the listing ID and review status.

Instructions

Submit an agent to the AgentPayStore marketplace for review. x402 compliance is REQUIRED for listing: the endpoint must serve a live 402 payment envelope (USDC on Base L2 via the x402 facilitator). Run marketplace_check_endpoint first to self-verify. Returns the listing id and review status.

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": {
      "name": "<name>",
      "description": "<description>",
      "endpoint_url": "<endpoint_url>",
      "price_per_call": "<price_per_call>",
      "developer_email": "<developer_email>",
      "payment_address": "<payment_address>"
    },
    "name": "marketplace_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
categoryNocustom
descriptionYes
endpoint_urlYes
price_per_callYes
developer_emailYes
payment_addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses the compliance gate, the payment rail (USDC on Base L2 via the x402 facilitator), and the return values. It does not cover review duration, whether resubmission is allowed, or any fee, which leaves the mutation side partially opaque.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the action, then the compliance constraint, then the return value. No filler or repetition of the tool name.

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 6-required-parameter write tool with no annotations and no schema descriptions, the definition is thinner than it should be; the return values are covered, but parameter contracts are not. An agent would still have to guess at formats for endpoint_url and payment_address before calling.

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 0% across 7 parameters, so the description must compensate and largely does not. It never explains units for price_per_call, the expected format of payment_address or endpoint_url, what category defaults to, or why developer_email is required.

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 gives a specific verb and resource ("Submit an agent to the AgentPayStore marketplace for review") and names the concrete outcome (listing id and review status). It is clearly distinguishable from siblings like marketplace_browse and marketplace_check_endpoint, which read rather than create listings.

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?

It states a hard prerequisite (x402 compliance, live 402 envelope) and explicitly routes the agent to marketplace_check_endpoint first to self-verify. What's missing is guidance on when not to submit or what happens on a failed review, but the pre-call path is clear.

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

Deploy Server

Other Tools