Skip to main content
Glama

request_quote

Request an instant total quote (item price + quote fee JPY 2,200 + handling fee + shipping, itemised). The quote fee is charged on issuance and is non-refundable even if you decline. 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.3/5.0
Behavior5/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 so: it discloses the exact non-refundable charge (JPY 2,200) at issuance, that a quote is non-binding and acceptance only moves to pending_review, and that a one-time access_token is returned which authorises accept/decline/status/evidence/messages. These are precisely the side effects and credential facts an agent needs before a costly irreversible call.

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?

Three sentences, front-loaded with purpose, followed by cost/irreversibility and then the token-handling requirement. No filler, though the middle sentences are long and pack multiple obligations (fee, non-reservation, pending_review) into single runs.

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?

For an 11-parameter mutation with no output schema and no annotations, the description covers the critical unknowns: cost, irreversibility, the resulting state, and the one-time token that gates the whole downstream flow. Minor gaps remain about how USD conversion and shipping overrides interact with the quoted total.

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 91%, so the schema already documents service_id, items[], details, hours, test_mode, etc. The description adds no per-parameter meaning beyond noting the itemised cost composition and the access_token return value, so the baseline of 3 applies.

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+resource ('Request an instant total quote') and immediately enumerates what the quote contains (item price, JPY 2,200 quote fee, handling fee, shipping, itemised). It also clarifies the downstream relationship to accept_quote/decline_quote, so an agent can distinguish this from its siblings without opening the schema.

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 gives strong when-to-use context: the fee is charged at issuance and is non-refundable even if declined, and getting a quote does not reserve execution. It stops short of explicit routing advice (e.g. call list_services first to obtain service_id, or choose queueing vs shopping_proxy), leaving some selection logic to the schema's enum descriptions.

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