Skip to main content
Glama

Nova Amazon MCP Server

get_vat_worksheet

Read-only

One VAT region's worksheet — the same rows as the dashboard table: a row per (account, ASIN, SKU) sold product with its CURRENT category (null = none). missingOnly=true applies the dashboard's own definition of missing (on a region Amazon prices, a product with a measured treatment is not missing). Use it to match a seller's tax-class file to exact SKUs/ASINs before building import_vat_categories rows. Server-side pagination: limit/offset, total returned.

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": {
      "region": "<region>"
    },
    "name": "get_vat_worksheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
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.
regionYesVAT region: 'EU' or 'UK' (a category only matters there).
accountsNoRestrict to a subset of your own seller account IDs (from list_accounts). Omit to include all your accounts. A brand/account name is accepted and resolved to its id when it matches one of your accounts unambiguously; a label that carries the id ("Brand (A1B2C3D4E5F6G)") resolves to that id.
missingOnlyNotrue = only products Nova has no VAT for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, non-destructive, closed-world), so the description's job is to add operational detail. It does: server-side pagination via limit/offset with a total returned, and the non-obvious fact that missingOnly uses the dashboard's own definition (a product with a measured treatment on an Amazon-priced region is not missing). Return format is described at row level.

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 returned shape, then the missingOnly nuance, then the intended use, then pagination — a sensible order with no filler sentences. It is dense (long parenthetical, several clauses) but each clause carries information an agent needs.

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 6-parameter read tool with no output schema, the description covers row grain, missing-only semantics, pagination and total, and the downstream import path. Nothing an agent needs in order to call it correctly or interpret the result is missing.

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 67%, and the description closes the most important gap: missingOnly is defined by the dashboard's 'missing' semantics rather than the schema's one-liner, and limit/offset are tied to server-side pagination with a total. It does not add anything for region or reason, but the schema already documents those.

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 names the resource precisely ('One VAT region's worksheet') and defines the row grain ('a row per (account, ASIN, SKU) sold product with its CURRENT category'), plus its relationship to the dashboard table. An agent can tell what this returns without opening the schema, and the 'worksheet' framing distinguishes it from query_* siblings.

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 states an explicit use case: match a seller's tax-class file to exact SKUs/ASINs before building import_vat_categories rows, which routes the agent to the follow-up tool. It also clarifies when to set missingOnly. There is no explicit when-not-to-use or comparison against the other get_*_worksheet siblings, keeping it short of a 5.

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.