Skip to main content
Glama

hou_tea_list_my_orders

List your USDC/x402 orders using your buyer list token, no merchant API key needed.

Instructions

[core] List USDC/x402 orders associated with the buyer_list_token (returned from a successful purchase or stored in env HOU_TEA_BUYER_LIST_TOKEN). No merchant API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buyer_list_tokenNo
statusNo
limitNo
offsetNo

Implementation Reference

  • The actual HTTP client implementation of listMyOrders — calls GET /api/v1/buyer/orders with Bearer token auth.
    listMyOrders: async (p: ListMyOrdersParams = {}) => {
      const token = (p.buyer_list_token ?? BUYER_LIST_TOKEN).trim();
      if (!token) {
        throw new Error(
          "buyer_list_token required: set env HOU_TEA_BUYER_LIST_TOKEN (from a successful buy response) or pass buyer_list_token to this tool."
        );
      }
      const q = qs({
        status: p.status,
        limit: p.limit,
        offset: p.offset,
      } as Record<string, unknown>);
      const url = `${DEFAULT_PAY_BASE}/api/v1/buyer/orders${q}`;
      const res = await fetch(url, {
        headers: {
          ...authHeaders(),
          Authorization: `Bearer ${token}`,
        },
      });
      if (!res.ok) {
        const text = await res.text().catch(() => "");
        throw new HouTeaHttpError(res.status, url, text);
      }
      return (await res.json()) as unknown;
    },
  • ListMyOrdersParams interface — defines the input parameters (buyer_list_token, status, limit, offset).
    export interface ListMyOrdersParams {
      /** Overrides `HOU_TEA_BUYER_LIST_TOKEN` for this call only. */
      buyer_list_token?: string;
      status?: string;
      limit?: number;
      offset?: number;
    }
  • Tool registration entry for hou_tea_list_my_orders in CORE_TOOLS array — includes name, group, inputSchema, and execute binding.
    {
      name: "hou_tea_list_my_orders",
      group: "core",
      summary: "List orders linked to buyer_list_token (Bearer auth).",
      description:
        "List USDC/x402 orders associated with the buyer_list_token (returned from a successful purchase or stored in env HOU_TEA_BUYER_LIST_TOKEN). No merchant API key required.",
      uiComponent: "OrderTimeline",
      inputSchema: obj({
        buyer_list_token: { type: "string" },
        status: { type: "string" },
        limit: { type: "integer", minimum: 1, maximum: 100, default: 20 },
        offset: { type: "integer", minimum: 0, default: 0 },
      }),
      execute: (args) =>
        houTea.listMyOrders(args as unknown as Parameters<typeof houTea.listMyOrders>[0]),
    },
  • nextAction reference from hou_tea_check_order — suggests calling hou_tea_list_my_orders after an order is confirmed/settled.
    if (status === "confirmed" || status === "settled") {
      return [
        {
          tool: "hou_tea_list_my_orders",
          reason: "Order confirmed; the buyer can now list / track their order history.",
        },
      ];
  • buildBuyBody helper — auto-registers buyer_list_token for grouping orders, enabling list_my_orders functionality.
    function buildBuyBody(
      product_name: string,
      unit_price: string,
      quantity: number
    ): Record<string, unknown> {
      const body: Record<string, unknown> = {
        product_name,
        unit_price,
        quantity,
        currency: "usdc",
      };
      if (!AUTO_BUYER_LIST) return body;
      if (BUYER_LIST_TOKEN) {
        body.buyer_list_token = BUYER_LIST_TOKEN;
      } else {
        body.register_buyer_list_token = true;
      }
      return body;
    }
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions the operation is a list (read) and authentication requirement, but it doesn't clarify error handling, pagination behavior, or any side effects, which is insufficient for a tool with four parameters.

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?

The description is a single concise sentence with no wasted words. It includes a useful [core] tag and front-loads the purpose. It could be slightly more structured but is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero schema descriptions and no output schema, the description is too brief. It omits return format, pagination details, error cases, and parameter constraints. A more complete description is needed for effective use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description should explain parameter meanings beyond names. Only buyer_list_token is hinted at in the description; status, limit, and offset are not explained. This is a significant gap.

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?

The description clearly states the tool lists orders associated with a buyer list token, specifying the resource and filter. However, it doesn't differentiate from sibling tools like hou_tea_check_order or hou_tea_browse, which could help an agent decide which tool to use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context on when to use it (after successful purchase, token from env) and notes no merchant API key is required. But it doesn't give explicit guidance on when not to use it or mention alternatives, leaving some ambiguity.

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/jackrain19743/hou-tea-mcp-server'

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