Skip to main content
Glama

Nova Amazon MCP Server

set_vat_default_category

Destructive

Set (or clear) ONE account's DEFAULT VAT category — the category every product without its own falls back to. 'A_NOVA_ZERO' is the zero-rated switch (VAT handled outside Nova, or VAT-free sales); a real code (e.g. 'A_GEN_STANDARD') applies one category to the whole catalog. TWO-STEP: call WITHOUT commit to preview current → new, show the user, then commit with the confirmationToken. category null clears the default. Requires the OAuth connection and the OWNER role.

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": {
      "account": "<account>",
      "category": "<category>"
    },
    "name": "set_vat_default_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
commitNoOmit/false = preview (no write). true = write; requires the confirmationToken from the preview.
reasonNoOne sentence, ALWAYS IN ENGLISH (regardless of the conversation language), on WHY you are making this call — the user question or your analytical goal. Recorded so the seller can see how their data is used.
accountYesThe seller account (seller_partner_id, or an unambiguous account name).
categoryYesA code from get_setup domain=vat `categories`, or null to clear the default.
confirmationTokenNoThe token the preview returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"A code from get_vat_setup `categories`, or null to clear the default."New value: +"A code from get_setup domain=vat `categories`, or null to clear the default."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the two-step preview/commit workflow, the need to show the user before committing, the OAuth connection and OWNER role requirement, and the effect of clearing or applying a category. These details materially affect how an agent should safely invoke this destructive mutation.

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 dense but front-loaded: it leads with the operation and default-category concept, then explains category semantics, the two-step workflow, clearing, and authorization. Every sentence contributes operational guidance.

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?

For a destructive 5-parameter mutation tool with no output schema, the description covers the essential context: preview/commit safety, authorization, clearing behavior, and category semantics. The preview result and confirmation token flow are explained sufficiently for correct invocation.

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 schema already documents all five parameters. The description still adds useful meaning about category values—especially that 'A_NOVA_ZERO' is the zero-rated switch and a real code applies one category to the whole catalog—beyond the schema's shorter category note.

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: set (or clear) ONE account's DEFAULT VAT category. It also explains the fallback behavior for products without their own category, distinguishing this from category import or worksheet tools.

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 usage context: use a preview call without commit first, show the user the change, then commit with the confirmationToken. It also explains the category choices and that null clears the default. It does not explicitly name alternative sibling tools or exclusion cases, so it falls short of a full when-to-use-vs-alternatives statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.