Skip to main content
Glama

Pay2GPT

Business: place orders

place_business_orders
Idempotent

For a company with a Pay2GPT business API key: open 1-100 orders of one product, each spending one of the company's credits for that product. Each order comes back with a redemption link for the end user. Reusing the same idempotency_key with the same arguments returns the same orders and spends nothing more. An order nobody has connected an account to can be given back with cancel_business_order.

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": {
      "product": "<product>",
      "quantity": "<quantity>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "place_business_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesProduct slug from business_credits
quantityYesHow many orders
idempotency_keyYesA unique key for this purchase, reused on retry

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the flags; the description explains what actually happens: credits are spent per order, each order yields a redemption link for the end user, and replaying the same idempotency_key with identical arguments returns the same orders without additional spend. It also discloses the reversibility condition (unconnected orders can be cancelled), which is the key operational caveat for a mutating tool.

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?

Four tight sentences, front-loaded with the prerequisite and scope, then cost, then idempotency, then the escape hatch. No filler and no repetition of annotation flags.

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?

With no output schema, the description still tells the agent what comes back (redemption links). Cost, idempotent retry behavior, and the cancellation path are all covered, which is everything needed to invoke this mutation correctly.

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 the baseline is 3, but the description adds real meaning: 'quantity' is clarified as the number of orders each consuming one credit for that product, and the idempotency key's retry semantics are spelled out rather than just 'reused on retry'. 'product' is tied to the business_credits listing, reinforcing the schema's slug hint.

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 1-100 orders of one product'), the cost model (one company credit per order), and the prerequisite (Pay2GPT business API key). It is clearly distinguishable from list_business_orders/get_business_order and explicitly hands off the reversal case to cancel_business_order.

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?

The prerequisite is stated up front and the description names the alternative (cancel_business_order) with the exact condition that selects it ('an order nobody has connected an account to'). It lacks explicit when-not guidance for the read-side siblings, but the create-vs-cancel boundary is unambiguous.

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