Skip to main content
Glama

Fish catalog

get_catalog
Read-onlyIdempotent

Get GYOTAK's full fish catalog with real-time availability, retail prices (THB/kg), freshness tiers, and traceability records. Retail prices are always included. For registered chat customers, pass customerKey (gyotak_cus_...) to show wholesale pricing and let them order with their saved details. For LINE VIP customers, pass lineUserId. Delivery is available within Thailand only. International addresses are not accepted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineUserIdNoLINE user ID for VIP pricing (optional)
customerKeyNoGYOTAK customerKey (gyotak_cus_...) for registered chat customers β€” identifies the customer, shows wholesale pricing and lets them order with their saved details (optional)

Output Schema

NameRequiredDescriptionDefault
vipNoCustomer line shown for a registered customer
itemsYesCatalog lines in the order shown (empty when no stock)
catalogNoUsed by the catalog widget (on-chain provenance per item)
nextActionsNoUsed by the catalog widget (buttons)
customerContextNoUsed by the catalog widget

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / customerKey / description
      Previous value: -"GYOTAK customerKey (gyotak_cus_...) for registered chat customers β€” enables identification, wholesale pricing, and one-tap checkout (optional)"New value: +"GYOTAK customerKey (gyotak_cus_...) for registered chat customers β€” identifies the customer, shows wholesale pricing and lets them order with their saved details (optional)"
    • removedOutput schema / properties / vip / properties / cashbackLimitThb
      Removed value: -{
      -  "type": "number"
      -}
    • removedOutput schema / properties / vip / properties / cashbackRemainingThb
      Removed value: -{
      -  "type": "number"
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "catalog": {
      +      "description": "Used by the catalog widget (on-chain provenance per item)",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "customerContext": {
      +      "description": "Used by the catalog widget",
      +      "type": "object"
      +    },
      +    "items": {
      +      "description": "Catalog lines in the order shown (empty when no stock)",
      +      "items": {
      +        "description": "One line of the catalog text",
      +        "properties": {
      +          "bands": {
      +            "additionalProperties": {
      +              "type": "integer"
      +            },
      +            "description": "Packs per weight band, as listed under πŸ“¦",
      +            "type": "object"
      +          },
      +          "catchRecordCount": {
      +            "description": "Number of catch records in the traceability line",
      +            "type": "integer"
      +          },
      +          "catchRecords": {
      +            "description": "Up to 3 catch records as listed",
      +            "items": {
      +              "properties": {
      +                "blogUrl": {
      +                  "type": "string"
      +                },
      +                "location": {
      +                  "type": "string"
      +                },
      +                "photoAt": {
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "photoAt"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "days": {
      +            "description": "Days tier shown next to the tier (LINE VIP order-page catalog only)",
      +            "type": "integer"
      +          },
      +          "fishName": {
      +            "type": "string"
      +          },
      +          "label": {
      +            "description": "Card label shown in parentheses (LINE VIP order-page catalog only)",
      +            "type": "string"
      +          },
      +          "onchain": {
      +            "description": "Midnight on-chain links as listed",
      +            "items": {
      +              "properties": {
      +                "moreRecords": {
      +                  "type": "integer"
      +                },
      +                "network": {
      +                  "type": "string"
      +                },
      +                "tier": {
      +                  "type": "string"
      +                },
      +                "url": {
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "network",
      +                "url"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "orderAs": {
      +            "description": "Status and tier to pass to place_order, as shown after β†’",
      +            "properties": {
      +              "status": {
      +                "type": "string"
      +              },
      +              "tier": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "status",
      +              "tier"
      +            ],
      +            "type": "object"
      +          },
      +          "orderUpToKg": {
      +            "description": "Shown as \"order up to …kg\"; 0 when shown as \"cannot be ordered by kg right now\"",
      +            "type": "number"
      +          },
      +          "packs": {
      +            "description": "Stock packs as shown",
      +            "type": "integer"
      +          },
      +          "preferred": {
      +            "description": "true when marked β˜… (preferred fish)",
      +            "type": "boolean"
      +          },
      +          "priceOnRequest": {
      +            "description": "true when the line shows \"price on request\"",
      +            "type": "boolean"
      +          },
      +          "priceThbPerKg": {
      +            "description": "Price shown for this line (THB/kg). Retail for anonymous callers, the customer's own price when vip is present",
      +            "type": "number"
      +          },
      +          "section": {
      +            "description": "Section heading (LINE VIP order-page catalog only)",
      +            "type": "string"
      +          },
      +          "status": {
      +            "description": "Cut / preparation as shown",
      +            "type": "string"
      +          },
      +          "thaiName": {
      +            "type": "string"
      +          },
      +          "tier": {
      +            "description": "Fresh / Tier1 / Tier2, or \"all\" for lines listed as [all tiers]",
      +            "type": "string"
      +          },
      +          "weightKg": {
      +            "description": "Stock weight as shown (kg, one decimal)",
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "fishName",
      +          "weightKg"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "nextActions": {
      +      "description": "Used by the catalog widget (buttons)",
      +      "type": "array"
      +    },
      +    "vip": {
      +      "description": "Customer line shown for a registered customer",
      +      "properties": {
      +        "cashbackLimitThb": {
      +          "type": "number"
      +        },
      +        "cashbackRemainingThb": {
      +          "type": "number"
      +        },
      +        "companyName": {
      +          "type": "string"
      +        },
      +        "orderMode": {
      +          "description": "LINE VIP order-page catalog: catalog browsing only / order from the LINE VIP order page / order in this chat",
      +          "enum": [
      +            "view_only",
      +            "line_order_page",
      +            "chat"
      +          ],
      +          "type": "string"
      +        },
      +        "shippingZone": {
      +          "description": "\"0\" = local (free), otherwise the zone number shown",
      +          "type": "string"
      +        },
      +        "tierPricing": {
      +          "description": "true when shown as \"tier pricing applied\"",
      +          "type": "boolean"
      +        }
      +      },
      +      "required": [
      +        "companyName"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "items"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real value on top: retail prices are always returned regardless of customer identity, wholesale pricing is conditional on credential type, and delivery is limited to Thailand with international addresses rejected. One ambiguity lingers: 'let them order with their saved details' hints at an ordering side effect on a tool annotated readOnlyHint=true, though it reads more as a downstream flow than a claim that this call writes data.

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?

Purpose is front-loaded in sentence one, followed by credential guidance and then the geographic constraint, which is a sensible order. Slight redundancy: retail prices are mentioned twice ('retail prices (THB/kg)' then 'Retail prices are always included'), costing a sentence without adding new information.

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?

An output schema exists, so return-value documentation is not required from the description. Given a two-parameter, read-only catalog tool, the description covers purpose, both credentials, pricing tiers, and the geographic restriction β€” everything an agent needs before calling it.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters already document their formats (gyotak_cus_..., VIP pricing), so the schema does the heavy lifting. The description reinforces the customerKey/lineUserId semantics and adds the assurance that retail prices are always included, but supplies no new format, precedence, or conflict-resolution rule for what happens if both are passed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('Get GYOTAK's full fish catalog') and enumerates the payload semantics: real-time availability, retail prices in THB/kg, freshness tiers, traceability records. This is concrete enough to distinguish it from verify_* or order-history siblings, but it never names search_fish, so the boundary between browsing the full catalog and searching it is left implicit.

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?

Gives clear conditional routing for both optional parameters: pass customerKey for registered chat customers to unlock wholesale pricing, pass lineUserId for LINE VIP customers. It also states the Thailand-only delivery constraint up front. It stops short of 5 because it never states when NOT to use this tool (e.g., versus search_fish for a narrower query).

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