Skip to main content
Glama

hou_tea_check_order

Check the current status of a tea order by its ID. Polls automatically until payment is confirmed via USDC settlement.

Instructions

[core] Poll the status of a previously created order. Status transitions: pending_payment → verifying → confirmed (after on-chain USDC settlement). Use exponential backoff (~2s, 4s, 8s …, max ~60s).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYes

Implementation Reference

  • The execute handler for 'hou_tea_check_order' — calls houTea.orderStatus with the order_id argument.
    execute: (args) => houTea.orderStatus(String((args as Record<string, unknown>).order_id)),
  • Input schema for 'hou_tea_check_order' — requires a single string parameter 'order_id'.
    inputSchema: obj({ order_id: { type: "string", minLength: 1 } }, ["order_id"]),
  • Full registration of 'hou_tea_check_order' as a core tool with metadata, input schema, execute function, and nextAction hint logic.
      name: "hou_tea_check_order",
      group: "core",
      summary: "Poll order status (pending_payment → confirmed).",
      description:
        "Poll the status of a previously created order. Status transitions: pending_payment → verifying → confirmed (after on-chain USDC settlement). Use exponential backoff (~2s, 4s, 8s …, max ~60s).",
      uiComponent: "OrderTimeline",
      inputSchema: obj({ order_id: { type: "string", minLength: 1 } }, ["order_id"]),
      execute: (args) => houTea.orderStatus(String((args as Record<string, unknown>).order_id)),
      nextAction: (_args, data) => {
        if (!isObject(data)) return undefined;
        const status = (data.status ?? data.order_status) as string | undefined;
        if (status === "confirmed" || status === "settled") {
          return [
            {
              tool: "hou_tea_list_my_orders",
              reason: "Order confirmed; the buyer can now list / track their order history.",
            },
          ];
        }
        return undefined;
      },
    },
  • HTTP client helper — makes a GET request to /api/v1/orders/:order_id to fetch the order status.
    orderStatus: async (order_id: string) => {
      return getJson<unknown>(`${DEFAULT_PAY_BASE}/api/v1/orders/${encodeURIComponent(order_id)}`);
    },
Behavior3/5

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

With no annotations, the description discloses status transitions and backoff strategy, but omits potential side effects or authentication needs. It adds value beyond schema but is not fully transparent.

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?

Two sentences, 37 words, front-loaded with purpose. No wasted words, efficient structure.

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

Completeness3/5

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

Given the simple tool (1 param, no output schema, no annotations), the description covers status transitions and polling strategy, but could mention what the response contains to be fully complete.

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?

The single parameter order_id is not described beyond its existence. With 0% schema description coverage, the description should compensate but adds no detail about the parameter's format or semantics.

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 states the action 'Poll' and resource 'status of a previously created order', distinguishing it from sibling tools like hou_tea_browse or hou_tea_explain.

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 description provides clear context on when to use (polling order status) and explicit timing advice (exponential backoff), but does not explicitly mention when not to use or alternatives.

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