Skip to main content
Glama

GYOTAK Fish Market

by com.thaifishsashimicatalog

place_order

Place an order. Two modes: (A) VIP wholesale: provide lineUserId of a registered VIP customer. (B) Guest retail: provide customerName, phone, items array, and a delivery address — shippingAddress, shippingProvince and email are all required, and an order missing any of them is rejected. Guest orders are priced at tier-linked retail rates (server-calculated) and the total is final at this point; a confirmation email with a PromptPay QR follows. Inventory is NOT deducted — orders go to the pick queue for staff fulfillment. Delivery is available within Thailand only, so the province must be a Thai one. International addresses are not accepted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNo(Guest mode, optional) Language of the confirmation email. Defaults to en.
memoNo(Optional) Order notes
emailNo(Guest mode) Email address for the order confirmation — required for guest orders
itemsNo(Guest mode) Order items
phoneNo(Guest mode) Contact phone number
fishNameNo(VIP mode) Fish name (romaji)
totalThbNo(VIP mode) Total amount in THB
lineUserIdNoLINE user ID of VIP customer (VIP mode). Omit for guest mode.
referrerIdNo(Optional) Referrer ID for tracking
customerKeyNo(Guest mode) Registered customer key (from register_customer). Resolves name/phone/shipping automatically. If you are connected through a personal token URL the customer is already resolved: send items[] alone and omit this, customerName, phone and lineUserId.
requestedKgNo(VIP mode) Requested weight in kg
customerNameNo(Guest mode) Customer name
shippingAddressNo(Guest mode) Street address and building name — required for guest orders
shippingDistrictNo(Guest mode, optional) District name
shippingProvinceNo(Guest mode) Thai province name, used for shipping cost — required for guest orders. Thailand only.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The description discloses key behavioral traits beyond annotations: guest orders are tier-linked retail, total is final, inventory is not deducted, orders go to the pick queue, and delivery is Thailand-only. It doesn't mention all side effects (e.g., whether VIP mode also sends confirmation), but it covers the most important ones.

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 dense but well-structured, front-loading the two modes and then covering requirements and consequences in a logical order. Every sentence adds value; no fluff or repetition.

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?

Given 15 parameters, no output schema, and no annotations, the description carries a heavy burden—and it largely succeeds. It covers mode selection, required fields, rejection conditions, pricing, inventory behavior, delivery constraints, and confirmation follow-up. A few minor gaps (e.g., exact response shape) exist, but the core calling context is 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 coverage is 100%, but the description adds meaning beyond the schema: it groups parameters by mode (VIP vs guest), explains when to omit customerName/phone/lineUserId (personal token URL), and clarifies required-ness that the schema doesn't enforce (0 required). It doesn't fully define every parameter, but the schema already documents them.

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 clearly identifies the tool's purpose—placing an order—and distinguishes two modes (VIP wholesale and guest retail) with distinct required parameters. It also differentiates from sibling tools like check_payment_status or confirm_payment by focusing on order creation.

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?

The description explicitly states when to use each mode, lists required fields for guest mode, notes when a personal token URL resolves the customer, and even excludes international addresses. It also says what happens next (pick queue, confirmation email), giving clear context for use.

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

All GYOTAK Fish Market toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Each tool has a clear role in the customer, ordering, payment, or verification flow. The only potential confusions (get_catalog vs search_fish, get_catch_reports vs verify_catch) are explicitly differentiated in their descriptions.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern using verbs like get, create, place, verify, check, and ask. Brand-specific tools like ask_gyotak and contact_gyotak still fit the same convention.

Tool Count4/5

18 tools is slightly on the heavy side for a single server, but the scope spans sales, payments, customer management, and blockchain traceability, so most tools have distinct jobs. It is above the ideal range but not bloated.

Completeness4/5

The core commerce loop (register, order, pay, confirm) and traceability verification are covered well. Missing order cancellation, guest order status retrieval, or customer profile editing are minor gaps that agents can usually work around.

Resources