ICONIC Agent-Native Marketplace — Seven Specialist Services

Begin Checkout

marketplace_begin_checkout

Destructive

Release Stripe-hosted fixed-price payment link ONLY after merchant/seller approval.

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": {
      "order_id": "<order_id>",
      "order_access_token": "<order_access_token>"
    },
    "name": "marketplace_begin_checkout"
  }
}

Input Schema

Name	Required	Description	Default
`order_id`	Yes
`order_access_token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare destructive=true, openWorld=true, and readOnly=false. The description adds a meaningful approval gate beyond those annotations, but it does not explain what releasing the link changes, whether it is reversible, or what auth/order-token requirements exist.

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?

The single sentence is front-loaded and free of filler. It is arguably too terse for a destructive checkout tool, but conciseness itself is strong.

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 open-world destructive tool with two required undocumented parameters and no output schema, the description gives only an approval prerequisite. It omits order token semantics, release consequences, and return behavior, leaving significant gaps.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention order_id or order_access_token at all. The required parameters remain undocumented beyond their names and titles.

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 action and resource: release a Stripe-hosted fixed-price payment link. It is understandable on its own, but it does not explicitly connect the action to beginning checkout or distinguish it from similarly named checkout/prepare siblings.

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?

Provides a clear prerequisite and exclusion: use only after merchant/seller approval. It does not name alternative tools or explain how approval is verified, so it is short of fully explicit when/when-not/alternatives guidance.

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

All ICONIC Agent-Native Marketplace — Seven Specialist Services 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?