Skip to main content
Glama

Tanatasa Beauty

by sg.tanatasa
OverviewDiscussionsAdmin

quote_cart

Read-onlyIdempotent

Price the cart now: current prices, discounts, stock, free Singapore delivery (shipping 0) and the delivered total in SGD cents, with buyer_summary to show the buyer. Stock is not reserved. coupon_code previews a coupon or a friend's referral code without saving it. With account_token, applies the customer's cashback credit unless use_credit is false. Next: create_checkout with this version and total.

Input Schema

NameRequiredDescriptionDefault
cart_idYescart_id from create_cart.
use_creditNoUse the signed-in customer's cashback credit (default true).
coupon_codeNoA coupon code or a friend's referral code to apply; null removes both. quote_cart previews it; create_checkout applies it.
guest_tokenNoPrivate guest session token from create_cart. Retain for cart, checkout and purchase-status calls; no account login needed.
account_tokenNoPrivate account token from sign_in, after the customer gave you the code from their email. Lets quotes and checkout use their cashback credit, and opens their orders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / account_token / description
      Previous value: -"Private account token from sign_in, after the customer gave you the code from their email. Lets quotes and checkout use their cashback credit."New value: +"Private account token from sign_in, after the customer gave you the code from their email. Lets quotes and checkout use their cashback credit, and opens their orders."
    • addedInput schema / properties / cart_id / description
      Added value: +"cart_id from create_cart."
  2. Changed2 schema fields changed
    • changedInput schema / properties / account_token / description
      Previous value: -"Private account token from verify_login_code, after the customer gave you the code from their email. Lets quotes and checkout use their cashback credit."New value: +"Private account token from sign_in, after the customer gave you the code from their email. Lets quotes and checkout use their cashback credit."
    • addedInput schema / properties / coupon_code
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 64,
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "A coupon code or a friend's referral code to apply; null removes both. quote_cart previews it; create_checkout applies it."
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / account_token
      Added value: +{
+  "description": "Private account token from verify_login_code, after the customer gave you the code from their email. Lets quotes and checkout use their cashback credit.",
+  "pattern": "^tak_[a-f0-9]{64}$",
+  "type": "string"
+}
    • addedInput schema / properties / use_credit
      Added value: +{
+  "description": "Use the signed-in customer's cashback credit (default true).",
+  "type": "boolean"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / guest_token
      Added value: +{
+  "description": "Private guest session token from create_cart. Retain for cart, checkout and purchase-status calls; no account login needed.",
+  "pattern": "^[a-f0-9]{64}$",
+  "type": "string"
+}
  5. Changed1 schema field changed
    • removedInput schema / properties / guest_token
      Removed value: -{
-  "description": "Private guest session token from create_cart. Retain for cart, checkout and purchase-status calls; no account login needed.",
-  "pattern": "^[a-f0-9]{64}$",
-  "type": "string"
-}
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing that stock is not reserved, that a coupon is previewed without being saved, and that cashback credit is applied only when account_token is present unless use_credit is false. These are exactly the side-effect nuances an agent needs before pricing.

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?

Front-loaded with the outcome and packed with useful detail, but the single dense run-on sentence with a trailing 'Next:' cue is slightly crowded. Every clause still carries information, so waste is minimal.

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

Completeness5/5

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

No output schema exists, yet the description enumerates what comes back (prices, discounts, stock, shipping 0, total in SGD cents, buyer_summary) and tells the agent the next call. Nothing material is missing for a 5-param quote tool.

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 behavioral meaning the schema cannot: use_credit only matters with account_token, and coupon_code is preview-only here. cart_id and guest_token handling are left to the schema.

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?

States a specific verb ('Price the cart now') plus the exact outputs: current prices, discounts, stock, Singapore delivery, delivered total in SGD cents, and buyer_summary. This differentiates it cleanly from siblings like get_cart (read state) and create_checkout (commits the order).

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?

Explicitly says coupon_code only previews here while create_checkout applies it, and closes with 'Next: create_checkout with this version and total', giving clear sequencing. It stops short of naming get_cart or explaining when a quote is unnecessary, but the routing is unambiguous.

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

All Tanatasa Beauty 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