Skip to main content
Glama

Moqway

Place an order

place_order
DestructiveIdempotent

Places the order for a quote. If it is within the buyer's spending rules, payment is captured into escrow (released to the supplier only after delivery) and status is 'paid'. Otherwise status is 'pending_approval' and approval_url must be shown to the human; you cannot approve it. Calling again with the same quote_id returns the same order. Ship-to defaults to the buyer's saved address.

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": {
      "quote_id": "<quote_id>"
    },
    "name": "place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
ship_toNoDelivery address; omit to use the buyer's default
quote_idYes
buyer_referenceNoYour PO or store order number, printed on documents

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description explains the spending-rule check, escrow capture and release timing, the pending_approval branch, the requirement to surface approval_url to a human, and that the agent cannot approve the order itself. It also explains idempotency for repeated quote_id calls and the default ship-to behavior.

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?

The description is front-loaded with the primary action and then layers in the payment branch, approval constraint, idempotency, and address default. Every sentence contributes necessary operational information without filler.

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?

For a complex mutation with no output schema, the description covers the main outcomes, statuses, approval behavior, idempotency, and address default well. It still leaves out error scenarios such as expired or invalid quotes and does not explain buyer_reference, but the core call behavior is sufficiently complete.

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 description coverage is 67%, so the schema already carries some parameter meaning. The description adds important semantics for quote_id (idempotent order creation) and ship_to (defaults to the saved address), though it does not explain buyer_reference.

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 opens with a specific verb and resource: 'Places the order for a quote.' That distinguishes placing an order from quote retrieval, cancellation, and the other sibling operations without requiring the reader to inspect the schema.

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?

Usage context is clear: this is the tool that converts a quote into an order and handles payment or approval. It does not explicitly name alternatives such as quote_order or cancel_order, but the quote-based scope and approval flow make the appropriate situation clear.

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