Skip to main content
Glama

alopeyk_create_order

Create a real delivery order to dispatch a courier and charge your account. Confirm addresses, transport type, and price before calling.

Instructions

Create a REAL delivery order — WARNING: this is billable.

Persian purpose: ثبت یک سفارش واقعی. On-Demand, requires an access_token AND enable_ordering=true (and read_only=false) on the instance; otherwise it returns {"error": "ordering_disabled", ...} without contacting the API. Maps to POST /api/v2/orders.

Dispatches a courier and charges the account. Confirm the addresses, transport type, and price (via alopeyk_get_price) before calling.

Args: transport_type: Vehicle class (motorbike, motor_taxi, cargo, cargo_s, car). addresses: Ordered stops, each {type, lat, lng} — one origin and one or more destinations. has_return: Whether the courier returns to origin (default false). cashed: Whether the delivery is cash-on-delivery (default false). scheduled_at: Optional ISO timestamp to schedule the pickup. discount_coupon: Optional discount coupon code to apply. instance: Configured instance to use (default when omitted).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transport_typeYes
addressesYes
has_returnNo
cashedNo
scheduled_atNo
discount_couponNo
instanceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, description discloses key traits: billable, dispatches courier, charges account, error if ordering_disabled. Missing details on idempotency or cancellation, but adequate for a creation tool.

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?

Well-structured with warning, purpose, prerequisites, then parameter details. Front-loaded with critical info. Slightly verbose in repeating defaults that schema already provides, but overall efficient.

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?

Covers purpose, prerequisites, parameters, error conditions, and usage guidance. Output schema exists, so return values need not be described. Complete for a billable ordering tool.

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

Parameters5/5

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

All 7 parameters are described with meaning, constraints, and examples (e.g., addresses format, transport_type values). Compensates fully for 0% schema coverage.

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?

Description clearly states it creates a real delivery order (billable), maps to POST /api/v2/orders, and distinguishes from siblings like alopeyk_get_price and alopeyk_cancel_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?

Provides clear context: requires access_token, enable_ordering=true, and advises to confirm addresses/price via alopeyk_get_price before calling. Does not explicitly state when not to use, but context is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dwin-gharibi/alopeyk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server