Skip to main content
Glama
Sign In

Remy Research MCP

by com.remyresearch
OverviewDiscussionsAdmin

quote_basket

Read-onlyIdempotent

For quote_basket and prepare_checkout only. Required on every call: country (AE), emirate (buyer-selected destination) and items (the complete basket). Each item requires id and qty. Ask the buyer for any missing destination or quantity before calling; use search_products to resolve exact orderable product IDs. Never guess missing values. Create or update a quote by supplying the COMPLETE desired basket. Add/remove/change items in that list and call again. UAE only. For Research Use Only. This research-use-only catalogue is for buyers 21+ years of age and is supplied for research purposes only. Not for human or veterinary use. Includes the selected emirate’s delivery estimate, cutoff and fee explanation. Does not store or submit an order. Send these fields inside tools/call params.arguments. Both basket tools are stateless: send the complete basket again, combining duplicate IDs. Do not send prices, totals, consent or approval flags. If a call returns INVALID_ARGUMENTS, follow missingFields (when present) and nextAction; correct invalid values or collect missing information before retrying with the complete basket. Dubai and qty 1 are examples, not defaults; replace them with the buyer-selected emirate and quantity, and replace PRODUCT_ID_FROM_SEARCH with an orderable id from search. Do not send buyer details to quote_basket. Example arguments: {"country":"AE","emirate":"Dubai","items":[{"id":"PRODUCT_ID_FROM_SEARCH","qty":1}]}

Input Schema

NameRequiredDescriptionDefault
itemsYesRequired COMPLETE desired basket of 1–20 distinct variant IDs. Combine the same ID into one line; send the entire updated basket on every call.
countryYesRequired delivery country code: AE means United Arab Emirates.
emirateYesRequired buyer-selected destination. Use an exact listed emirate; ask the buyer if unknown, never assume Dubai.
promoCodeNoOptional buyer-supplied promotion code, up to 24 letters or digits. Omit when absent; do not invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / items / description
      Previous value: -"The COMPLETE desired basket of 1–20 distinct variant IDs. Combine the same ID into one line; send the entire updated basket on every call."New value: +"Required COMPLETE desired basket of 1–20 distinct variant IDs. Combine the same ID into one line; send the entire updated basket on every call."
    • changedInput schema / properties / items / items / properties / id / description
      Previous value: -"Exact id from the latest search_products result, not sku, product name or URL. Select an orderable variant."New value: +"Required exact id from the latest search_products result, not sku, product name or URL. Select an orderable variant."
    • changedInput schema / properties / items / items / properties / qty / description
      Previous value: -"Quantity as a JSON integer from 1 to 10, for example 2, not \"2\". The field is qty, not quantity."New value: +"Required buyer-selected quantity as a JSON integer from 1 to 10, for example 2, not \"2\". The field is qty, not quantity. Ask the buyer if unknown; there is no default quantity."
  2. Changed6 schema fields changed
    • addedInput schema / properties / country / description
      Added value: +"Required delivery country code: AE means United Arab Emirates."
    • addedInput schema / properties / emirate / description
      Added value: +"Required buyer-selected destination. Use an exact listed emirate; ask the buyer if unknown, never assume Dubai."
    • addedInput schema / properties / items / description
      Added value: +"The COMPLETE desired basket of 1–20 distinct variant IDs. Combine the same ID into one line; send the entire updated basket on every call."
    • addedInput schema / properties / items / items / properties / id / description
      Added value: +"Exact id from the latest search_products result, not sku, product name or URL. Select an orderable variant."
    • addedInput schema / properties / items / items / properties / qty / description
      Added value: +"Quantity as a JSON integer from 1 to 10, for example 2, not \"2\". The field is qty, not quantity."
    • addedInput schema / properties / promoCode / description
      Added value: +"Optional buyer-supplied promotion code, up to 24 letters or digits. Omit when absent; do not invent one."
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, which is potentially in tension with 'Create or update a quote', but the description resolves this by stating it is stateless and does not store or submit an order. It further discloses the error contract (INVALID_ARGUMENTS with missingFields and nextAction), what not to send (prices, totals, consent flags), and what comes back (delivery estimate, cutoff, fee explanation).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The required-fields guidance is front-loaded, but the text is long and repeats the research-use-only restriction twice in near-identical wording ('For Research Use Only' and 'This research-use-only catalogue is for buyers 21+...'). Multiple sentences overlap on statelessness and the complete-basket rule.

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 a stateless 4-parameter tool with no output schema, this covers required inputs, error recovery, statelessness, and the returned delivery estimate and fee information. The only weak spot is the ambiguous opening clause, which does not clarify when this tool rather than prepare_checkout is the right terminal call.

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 100%, so the baseline is 3, but the description adds real semantics: the basket must be complete and duplicate IDs combined, the example values are not defaults, and buyer-derived values must never be guessed. It omits promoCode entirely, leaving that parameter to the schema alone.

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 sentence 'Create or update a quote by supplying the COMPLETE desired basket' gives a specific verb and resource, and the description separates it from prepare_checkout ('Does not store or submit an order'). The opening phrase 'For quote_basket and prepare_checkout only' is confusing and restates the tool name rather than adding scope information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent: use search_products to resolve orderable IDs, ask the buyer for missing destination or quantity, never guess, UAE only, and re-send the complete basket on updates. It also names a hard exclusion ('Do not send buyer details to quote_basket') and a sibling boundary against prepare_checkout.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Remy Research MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources