Skip to main content
Glama

Nova Amazon MCP Server

get_fbm_worksheet

Read-only

One delivery zone's per-product FBM worksheet: a row per (account, ASIN, SKU) catalog product with its channel (isFbm), L24M sales and the CURRENT per-product override for that zone (currentCost null = the product falls on the seller's rate book). Use it to match a seller's per-product shipping file to exact SKUs/ASINs before building import_fbm_costs rows. Defaults to FBM products only (fbmOnly=false includes FBA); missingOnly=true keeps rows without an override. Paginate with limit/offset.

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": {
      "zone": "<zone>"
    },
    "name": "get_fbm_worksheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneYesDelivery zone: an ISO-3166 alpha-2 country ('DE', 'GB' — never 'UK') or 'ROW' (rest of world).
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.
fbmOnlyNotrue (default) = merchant-fulfilled products only.
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 without a per-product override for this zone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations (readOnlyHint=true, destructiveHint=false, openWorldHint=false) already cover the safety profile, so the description adds value by disclosing defaults and semantics: 'currentCost null = the product falls on the seller's rate book', fbmOnly defaults to true, and missingOnly keeps rows lacking an override. It does not mention row counts, response size, or ordering, but the disclosed defaults and null behavior are the behaviors an agent most needs here.

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?

A single dense paragraph that is sensibly ordered: row shape first, then the use case, then defaults, then pagination. Every clause carries information, though the sentences are long enough that an agent must parse carefully rather than skim a bullet structure.

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?

With no output schema and a required zone parameter, the description supplies the return shape (one row per account/ASIN/SKU with channel, L24M sales, current override), the null semantics of the key field, the filter defaults, and pagination guidance. What is missing is only peripheral — result ordering, approximate row volume, and the meaning of the reason/accounts parameters.

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 71%, and the description fills the higher-value gaps: it explains that fbmOnly defaults to FBM-only, that missingOnly filters to products without a zone override, and that limit/offset are for pagination. It adds the output-side meaning of currentCost=null, which the schema cannot express. It does not touch the reason or accounts parameters, but the schema documents those adequately.

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 exact resource and its grain: 'One delivery zone's per-product FBM worksheet: a row per (account, ASIN, SKU) catalog product' with the columns returned (channel, L24M sales, current override). That level of specificity separates it immediately from the sibling worksheet readers (get_cogs_worksheet, get_vat_worksheet, get_tags_worksheet) without needing to open any 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?

It gives a concrete use case — matching a seller's per-product shipping file to exact SKUs/ASINs before building import_fbm_costs rows — which implicitly names the downstream alternative. It does not state when NOT to use it (e.g., versus get_cogs_worksheet or import_fbm_zone_rates), so the exclusion side is left to inference.

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.