Skip to main content
Glama

Nova Amazon MCP Server

list_cost_inputs

Read-only

List the seller's CONFIGURED per-SKU input values — the raw values the seller entered (source of truth, not the aggregated metric). type selects which: 'cogs' (cost of goods, default), 'fbm' (merchant-fulfilment cost — the seller's rate book at level 'zone': shipping per delivery country or 'ROW', packing per parcel and picking per unit; then per-product rows at level 'sku'), or 'vat' (VAT product category). Use it to audit setup: spot placeholder / negative / implausible costs, cost entered per lot vs per unit (COGS quantity), wrong or missing VAT categories, or SKUs missing an input. Filter by skus to inspect specific products. To FIX missing or wrong COGS, use import_cogs (two-step, with user approval).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cost_inputs"
  }
}

Input Schema

NameRequiredDescriptionDefault
skusNoRestrict to these SKUs.
typeNoWhich input to audit. Defaults to 'cogs'.
limitNo
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.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and closed-world, so the safety profile is covered; the description still adds real value by stating the data is the raw seller-entered source of truth and by spelling out the hierarchical levels returned for 'fbm' ('zone' shipping/packing/picking rows, then per-SKU rows). It does not describe pagination or default ordering behavior, which keeps it off a 5.

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 core identity and the raw-vs-aggregated distinction, then the type taxonomy, then usage and the fix alternative — a sensible information order. The dense parentheticals around 'fbm' are hard to parse in one pass but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return-shape burden; it partially does by explaining the raw value concept and the 'zone' vs 'sku' levels for fbm, but it never describes what a row or field looks like for 'cogs' or 'vat' results. For a zero-required-param audit tool with five params this is adequate but leaves the agent guessing at response structure.

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 80%, so the schema already documents `skus`, `type` (with enum), `reason`, and `accounts` thoroughly. The description elaborates meaningfully on what each `type` value contains, but leaves `limit` and the account resolution behavior entirely to the schema, so it adds only partial value over structured data.

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?

States a specific verb and resource ('List the seller's CONFIGURED per-SKU input values') and immediately distinguishes them from the aggregated metric, clarifying what class of data this is. The three-way `type` breakdown (cogs/fbm/vat) makes the scope concrete enough that an agent knows exactly what it gets back without opening the 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?

Gives a clear use case (audit setup: placeholder/negative/implausible costs, per-lot vs per-unit entry, missing VAT categories) and an explicit handoff for the fix path ('use import_cogs (two-step, with user approval)'). It does not address the closely-named worksheet siblings (get_cogs_worksheet, get_vat_worksheet, get_fbm_worksheet), which is the main unresolved routing ambiguity.

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.