Skip to main content
Glama

MARU Japan Hands

Place a takeout order

place_takeout_order

Place a takeout order. Returns an order number and a link. The customer pays at pickup at the counter, or opens the link to pay with JPYC (discounted). This tool never charges or moves money.

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": {
      "shop": "<shop>",
      "items": "<items>",
      "pickup_time": "<pickup_time>",
      "name": "<name>"
    },
    "name": "place_takeout_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName for the order
shopYes
itemsYes
contactNoPhone or email for the shop to reach the customer
pickup_timeYesPickup time today in JST, HH:MM

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive write with openWorldHint, so the safety bar is partly covered. The description adds genuinely useful context beyond them: the tool never charges or moves money, and payment happens at pickup or via a JPYC link. It does not address retry behavior or what happens if pickup_time is unavailable, though idempotentHint=false already signals duplicates are possible.

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?

Three short sentences, front-loaded with the action, then the return value, then the payment behavior. Every sentence carries distinct information and nothing is repeated from the schema or annotations.

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

Completeness4/5

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

With no output schema, the description correctly fills the gap by stating the return value (order number and link) and the payment model. Given the tool creates a real order, more on failure modes or pickup_time constraints would help, but the essentials for calling it are present.

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 60%, and the description itself adds no parameter-level detail such as where the shop value comes from or how options are chosen. The nested item structure and pickup_time format are documented in the schema, so the baseline of 3 is appropriate, but the undescribed 'shop' field remains unexplained in both places.

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?

States a specific verb and resource ('Place a takeout order') and names what comes back (order number and a link), so an agent can tell it apart from read-only siblings like get_menu or check_availability. It does not explicitly say how it differs from other ordering or quote tools, but the action is unambiguous.

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?

Usage is implied by the verb and by the payment note (no money moves, customer pays at pickup or via link), which tells the agent no payment step is needed. There is no explicit when-to-use or when-not guidance, no prerequisite such as calling get_menu or check_availability first, and no mention of how to handle a failed or duplicate submission.

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.