Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Set up tax

configure_tax
Idempotent

Decide how a store charges tax: mode "none", "manual" (your own manual_rates per country/region, as percentages), "gst_in" for Indian businesses (with gstin, gst_business_state and gst_rate_percent; CGST+SGST or IGST is worked out per order), or "stripe_tax". prices_include_tax says whether catalogue prices already include tax. Only the fields you pass change. Ask the user for their tax registration details — never invent a GSTIN or a rate.

Input Schema

NameRequiredDescriptionDefault
modeNo"none", "manual" (your own rates per country/region), "gst_in" (India GST: CGST+SGST in-state, IGST across states) or "stripe_tax" (needs Stripe as the payment provider)
gstinNomode "gst_in": the business GSTIN (15 characters), printed on invoices; null clears
site_idYesThe site, from list_sites
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.
manual_ratesNomode "manual": the full list of rates (replaces the current list)
gst_rate_percentNomode "gst_in": default GST rate, e.g. 18
gst_business_stateNomode "gst_in": the state the business is registered in, e.g. "MH" — decides CGST+SGST vs IGST
prices_include_taxNotrue when catalogue prices already include tax (common for India GST); tax is then shown, not added

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. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive operation. The description adds important behavioral context beyond annotations: only passed fields change, manual rates are percentages, and the agent must ask the user for tax registration details rather than inventing a GSTIN or rate.

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

Conciseness5/5

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

The description is front-loaded with the core decision and then enumerates the modes efficiently. Every sentence adds relevant detail, including the important constraint against inventing tax registration data.

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?

Given 8 parameters with full schema descriptions, annotations covering safety and idempotency, and no output schema, the description provides enough context to invoke the tool correctly. It covers mode selection, key GST behavior, partial-update semantics, and the critical warning about not fabricating tax details.

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. The description still adds useful domain meaning by explaining how modes relate to parameters: manual_rates are per country/region percentages, gst_in uses gstin, gst_business_state and gst_rate_percent, and prices_include_tax controls whether catalogue prices already include tax.

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 states a specific verb and resource: deciding how a store charges tax. It immediately distinguishes the four tax modes and their core semantics, so an agent can tell this apart from sibling configuration tools such as configure_payments or configure_shipping.

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 clear context for when to use the tool: setting up store tax behavior, with mode-specific guidance for manual, gst_in, and stripe_tax. It does not explicitly name when not to use it or compare it to adjacent configuration tools, but the intended usage is clear.

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