Skip to main content
Glama

Migawari

Request a quote

request_quote

Request an instant total quote (item price + quote fee JPY 2,200 + handling fee + shipping, itemised). Requesting a quote is free: the quote fee (JPY 2,200) is charged as part of the total when you accept, and is non-refundable once charged. Getting a quote does not reserve execution: accepting a quote only places the request in pending_review. The response includes an access_token shown only once: store it, it authorises accept/decline/status/evidence/messages for this quote.

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": {
      "service_id": "<service_id>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoArea / city in Japan, e.g. 'Akihabara', 'Ginza', 'Shibuya'.
hoursNoFor queueing: hours (minimum 1).
itemsNoFor shopping_proxy: items to buy.
notesNo
detailsNoService-specific details: store name/address, target items, photo subjects, restaurant name + party size + desired time (phone_reservation; venue_type must be 'restaurant'), queue location, package sender/destination, etc.
currencyNoUSD totals use the FX rate fixed at quote time.
requesterNoWho is asking: agent name and a contact the operator can reply to.
test_modeNoIf true, this is a test order: the flow is simulated and no payment is requested.
service_idYesCatalog service id (see list_services).
shipping_jpyNoOptional shipping override in JPY; defaults apply otherwise.
item_price_jpyNoAlternative to items[]: total item price, tax incl., JPY.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes well beyond that by disclosing the JPY 2,200 fee, when it is charged, that it is non-refundable, and that quoting creates no reservation. It also warns that the response carries an access_token shown only once which must be stored to authorise accept/decline/status/evidence/messages — exactly the operational facts an agent cannot infer from annotations.

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 sentences, front-loaded with the core action and total composition, then cost semantics, then the no-reservation caveat, then the access_token requirement. Dense but every sentence carries distinct operational value; it could be trimmed slightly but nothing is filler.

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 11 parameters, nested objects, and no output schema, the description covers the highest-risk gaps: cost timing, non-reservation, and the one-time access_token in the response. It does not sketch the rest of the response body, but the critical return-value fact is present, so it is nearly complete for this complexity.

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

Parameters4/5

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

Schema coverage is 91%, so the schema already does most of the work and a baseline of 3 would be defensible. The description adds genuine meaning by explaining how the monetary parameters compose into the returned total (item price plus quote fee plus handling fee plus shipping, itemised), which is context the schema fields do not spell out.

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 opens with a specific verb and resource — 'Request an instant total quote' — and immediately breaks down what the quote contains (item price + quote fee + handling fee + shipping, itemised). It also distinguishes the quote step from the downstream accept/decline/status/evidence/messages actions, so an agent can place it in the workflow without opening other schemas.

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?

It clarifies the key decision context: quoting is free, the fee only lands on accept, and a quote does not reserve execution (accepting only moves to pending_review). That tells an agent when this tool is the right first step, though it stops short of explicitly naming alternatives such as list_services for catalog lookup or a direct accept path.

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.