Skip to main content
Glama

AIDISH — AIエージェントから受取注文できる飲食店

place_pickup_order

受取注文(テイクアウト)を入れる。支払いは受取時に店頭(現金・カード・QR)。氏名と電話番号は必須で、店が受取時の本人確認と連絡に使う。注文前に必ず利用者に内容と受取時刻を確認すること。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "items": "<items>",
      "customer_name": "<customer_name>",
      "customer_tel": "<customer_tel>"
    },
    "name": "place_pickup_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
itemsYes
pickup_atNo受取希望時刻 ISO8601(省略時は最短)
tenant_idNo店舗ID(省略時は既定店)
customer_telYes利用者の電話番号(数字・ハイフン)
customer_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / items / items / properties / option_ids
      Added value: +{
      +  "description": "選んだオプションの id(list_menu の options[].choices[].id。required が true の組は必ず選ぶ・それ以外は任意)",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • removedInput schema / properties / items / items / properties / options
      Removed value: -{
      -  "description": "list_menu の option の id(任意)",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add useful behavior: payment is collected in-store at pickup (cash/card/QR), and the name and phone are used by the store for identity verification and contact. It does not disclose what happens after submission (order confirmation, failure/error handling, cancellation or modification policies).

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?

Four short sentences, each carrying distinct information (action, payment, required identity data, confirmation duty) with no filler. Front-loaded with the core action.

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?

For a mutation tool with no annotations and no output schema, the description covers payment, required customer data, and the confirmation obligation, which is reasonably complete. It still omits outcome behavior (what the agent gets back on success/failure) and any mention of the tenant/store default.

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 coverage is 50%. The description explains why customer_name and customer_tel are mandatory (identity verification and contact) and references confirming pickup time, adding meaning beyond the schema for those fields. It says nothing about note, tenant_id, or the item structure, leaving half the parameters to the schema.

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 opens with a specific verb+resource: placing a takeout/pickup order ('受取注文(テイクアウト)を入れる'). It is clearly distinguishable from the sibling lookup tools (check_pickup_availability, find_stores, list_menu), though it does not name them explicitly.

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?

It gives a concrete pre-call obligation ('注文前に必ず利用者に内容と受取時刻を確認すること') and states payment happens at pickup, which implies usage context. However, it never explains when to choose this tool over checking availability first or how it relates to the sibling tools.

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