Skip to main content
Glama

Submit by Hand

Order directory submission

create_order

Open an order and get a Stripe checkout link for the user to pay. Call it only after the user has chosen a plan, agreed to buy, and given the email address for the order (the order link and receipt go there). Nothing is charged by this call: the user opens checkout_url and pays on Stripe. Pass preview_id from draft_listing, or product_url to draft the listing in the same call.

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": {
      "plan": "<plan>",
      "email": "<email>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYeslaunch = 25 directories, starter = 50, growth = 100, pro = 200.
emailYesThe buyer's email address.
preview_idNoFrom draft_listing.
product_urlNoThe product website, when there is no preview_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well past the annotations by clarifying that nothing is charged here and that payment happens when the user opens checkout_url on Stripe — critical semantics for a non-read-only, open-world write. It does not warn that repeat calls are not idempotent and could open duplicate orders, which is the main residual gap.

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: purpose and return, then preconditions, then the parameter branching. The most important constraint (nothing is charged here) is stated immediately after the purpose, so it is front-loaded rather than buried.

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

Completeness4/5

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

With no output schema, the description compensates by naming checkout_url as the returned artifact and explaining the payment handoff. The only missing piece for a non-idempotent write is what to do on retry or duplicate submission.

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 already 100%, so the enum and lengths are documented. The description still adds cross-tool meaning the schema lacks: preview_id originates from draft_listing, product_url substitutes when no preview exists, and the email is where the order link and receipt are sent.

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?

States a specific verb and resource (open an order) plus the concrete outcome (get a Stripe checkout link). It is clearly distinguishable from draft_listing (which creates the preview) and get_order_status (which reads state), since this call is the one that opens the payable order.

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?

Gives explicit preconditions: the user must have chosen a plan, agreed to buy, and supplied the email address. It also states the alternative paths for the two optional parameters (preview_id from draft_listing, otherwise product_url), which is precisely the routing an agent needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources