Skip to main content
Glama

Nova Amazon MCP Server

get_stock_worksheet

Read-only

One stock region's replenishment worksheet — the rows of the Data Inputs 'Stocks' page as JSON: a row per (account, ASIN) that holds or sells stock in the region, with the row's OWN values (own: what import_stock_params wrote for that product × region), what each of the five parameters RESOLVES to (resolved: product row → product 'ALL' row → account default for the region → account default 'ALL'), where each came from (source: asin_region | asin_all | seller_region | seller_all | null = nothing → no recommendation), paramsComplete, and the velocity / FBA stock next to it. region 'ALL' lists the product × 'ALL' rows (where a production lead time naturally lives). Use it to match a seller's lead-time file to exact ASINs before import_stock_params; missingOnly=true keeps the products that still resolve nothing for at least one parameter. 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": {
      "region": "<region>"
    },
    "name": "get_stock_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.
regionYesA stock region as get_setup domain=stock lists them ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted) or 'ALL' (every region without its own row).
searchNoASIN or product name substring.
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 whose five RESOLVED parameters are not all set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / region / description
      Previous value: -"A stock region as get_stock_setup lists them ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted) or 'ALL' (every region without its own row)."New value: +"A stock region as get_setup domain=stock lists them ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted) or 'ALL' (every region without its own row)."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish this as a safe, closed read, so the description's value lies in disclosing the resolution cascade ('product row → product "ALL" row → account default for the region → account default "ALL"') and what a null source implies ('nothing → no recommendation'). It also flags the non-obvious region 'ALL' listing behavior. It omits pagination defaults or row-count expectations, so it stops short of fully describing response volume.

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?

It is front-loaded with the resource definition before the workflow guidance, and every clause carries information. The middle sentences are heavily nested with parentheticals and backticked field names, making it dense to parse, but little is genuinely redundant.

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, the description takes on the burden of explaining the return shape, and it does so thoroughly: row key, `own` values, `resolved`, `source` enum values, `paramsComplete`, and adjacent velocity/FBA stock. The main residual gap is pagination behavior beyond 'Paginate with limit/offset' — no default or cap guidance for a potentially large row set.

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 71%, below the 80% threshold, but the schema already documents region, missingOnly, accounts, and search in detail. The description largely restates the 'ALL' region and missingOnly semantics rather than adding new parameter meaning; its richest content (own vs resolved vs source) describes response fields, not inputs. Baseline 3 fits.

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 opening clause names a specific resource and its shape: 'One stock region's replenishment worksheet — the rows of the Data Inputs "Stocks" page as JSON.' It immediately clarifies granularity ('a row per (account, ASIN)'), which is enough to distinguish it from get_fbm_worksheet, get_cogs_worksheet, and get_supply_chain_products without opening 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 states a concrete use case and the downstream tool it precedes: 'Use it to match a seller's lead-time file to exact ASINs before import_stock_params,' plus the specialized mode 'missingOnly=true keeps the products that still resolve nothing.' It does not explicitly say when to prefer a sibling such as get_supply_chain_products instead, so routing is clear but not exhaustive.

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.