Grigora

update_commerce_settings

Destructive

Update store settings, most importantly the default currency for new products.

Payment gateway credentials cannot be set through this tool — connect a gateway in the Grigora dashboard. Existing connections are preserved.

Args: project_id: The project ID. store_name: Store display name. currency: Default ISO currency code for new products, e.g. USD. support_email: Buyer-facing support address. notification_email: Address that receives new-order notifications. payment_provider: Which connected gateway checkout uses: external, razorpay, stripe, paypal, paddle, paystack, gumroad, or manual. storefront_base_url: Overrides the base URL used to build product and collection links. checkout_mode: Checkout strategy. Default external_first. appearance: JSON object {theme_preset, accent_color, background_color, text_color, button_style, product_layout, media_fit}. seo_defaults: JSON object of fallback SEO for product and collection pages. shipping: JSON object of shipping rates and zones. tax: JSON object of tax rules. invoice: JSON object of invoice/receipt configuration.

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": {
      "project_id": "<project_id>"
    },
    "name": "update_commerce_settings"
  }
}

Input Schema

Name	Required	Description	Default
`tax`	No
`invoice`	No
`currency`	No
`shipping`	No
`appearance`	No
`project_id`	Yes
`store_name`	No
`seo_defaults`	No
`checkout_mode`	No
`support_email`	No
`payment_provider`	No
`notification_email`	No
`storefront_base_url`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true; the description adds real value by disclosing that gateway credentials cannot be set here and that existing connections are preserved. However, it never states whether omitted parameters preserve or clear existing values — a critical ambiguity for a destructive 13-parameter settings mutation where every field defaults to "" — and says nothing about required permissions.

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 purpose sentence, then a scoping caveat, then a compact Args block — well sized for 13 parameters. The Args list is dense but every line carries information; no filler or repetition of the name.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and all parameters are covered. What is missing is the mutation contract: partial-vs-full replacement semantics, whether an omitted field is preserved or reset, and permission/auth expectations for a destructive open-world write.

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

Parameters5/5

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

Schema coverage is 0% (bare string titles), so the description carries the full burden and does so well: it enumerates the eight allowed payment_provider values, gives checkout_mode's default of external_first, explains currency as an ISO code for new products, and describes the intent of each JSON blob (appearance, seo_defaults, shipping, tax, invoice). This adds substantial meaning the schema cannot convey.

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 ("Update store settings") and singles out the highest-impact field (default currency for new products). It is clearly distinguishable from product/variant/collection tools in the sibling list, though it never names get_commerce_settings or update_seo_settings as the read/adjacent counterpart.

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 resource (storefront configuration) and there is one explicit exclusion — payment gateway credentials must be connected in the Grigora dashboard. But there is no guidance on when to read settings first, whether this replaces or merges with current config, or how it relates to the many other update_* commerce tools.

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

All Grigora tools Inspect

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

Need Help?