Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Set up shipping zones and rates

configure_shipping
Destructive

Create, change or delete a store's shipping zones (which countries/regions it ships to) and the rates buyers choose from in each zone. One change per call. create_zone (name + countries) can carry its rate in the same call (price, plus free_over for free delivery from an amount) — prefer that. Otherwise create_rate in the zone (by zone_id or zone_name) with kind (inferred from price / free_over when omitted) — flat (price, optionally only between min_order and max_order), weight_bands or price_bands (bands of from/up_to/price), or free_over (price below the free_over amount, free from it up). Amounts are major currency units, weights grams; rates default to the store currency. A store with no zones charges no shipping; buyers outside every zone get no shipping option. Zone and rate ids are in get_store_settings.

Input Schema

NameRequiredDescriptionDefault
kindNoRate pricing: flat (one price, optionally only for orders between min_order and max_order), weight_bands / price_bands (`bands`), free_over (`price` below `free_over`, free from it up)
nameNoZone name ("India", "Rest of world") or rate name shown to buyers ("Standard delivery")
bandsNoweight_bands (grams) or price_bands (order amount) — first matching band wins
priceNoflat: the charge. free_over: the charge below the threshold. Major units.
actionYes
activeNoRate offered at checkout (default true)
rate_idNoFor update_rate / delete_rate
regionsNoOptional zone regions/states ("IN-MH"); null clears
site_idYesThe site, from list_sites
zone_idNoFor update_zone / delete_zone / create_rate (from get_store_settings or create_zone)
currencyNoRate currency; defaults to the store currency
countriesNoZone countries, ISO 3166-1 alpha-2 ("IN", "US")
free_overNofree_over: order amount (major units) from which shipping is free
max_orderNoflat only: offer this rate only up to this order amount
min_orderNoflat only: offer this rate only from this order amount
rate_nameNocreate_zone with a price: the name buyers see for the rate (default "Standard delivery")
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
zone_nameNocreate_rate: the zone by its name, when you do not have its id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / rate_name
      Added value: +{
+  "description": "create_zone with a price: the name buyers see for the rate (default \"Standard delivery\")",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / zone_name
      Added value: +{
+  "description": "create_rate: the zone by its name, when you do not have its id",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false, so the mutation risk is structured. The description adds genuine value by disclosing downstream consequences: a store with no zones charges no shipping, and buyers outside every zone get no shipping option — an agent can reason about the blast radius of delete_zone. It stops short of stating whether deletes are irreversible or what happens to rates when a zone is deleted.

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-loads what the tool does, then the preferred call shape, then the rate kinds and units. Dense but every clause carries actionable content; the parenthetical asides make it slightly harder to scan than a bulleted structure would.

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 18-parameter, action-discriminated mutation tool with no output schema, the description covers the action-to-parameter mapping, units, defaults, and where to obtain zone/rate ids. Remaining gap is update semantics: whether omitting a field on update_zone/update_rate clears it or leaves it unchanged.

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 coverage is 94%, so the baseline is 3. The description does add cross-parameter logic the schema cannot express — kind is inferred from price/free_over when omitted, and which parameters belong to which action — plus unit conventions (major currency units, weights in grams, default store currency), which is real added meaning.

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 set (create/change/delete) over two named resources (shipping zones and the rates within them), and immediately delimits the concept of a zone (which countries/regions it ships to). An agent can distinguish this from configure_tax, configure_payments and get_store_settings 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?

Gives concrete operating rules: 'One change per call', prefer create_zone carrying its rate, otherwise create_rate addressed by zone_id or zone_name. It routes between its own actions but never says when not to use this tool or who can call it (permission prerequisites).

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

All Mondovo 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