Skip to main content
Glama

Nova Amazon MCP Server

list_metrics

Read-only

List the metrics Nova can report (key, label, unit type, whether higher is better). Call this first to discover valid metric keys for the other tools. When your accounts include a Vendor Central (1P) account, each metric also carries channels: the Amazon programmes it exists on, SELLER = Seller Central (3P), VENDOR = Vendor Central (1P); the Vendor Central metrics are listed too, each with its basis: 'sell-out' = Amazon's measures of what it shipped, 'sell-in' = the vendor's P&L (its top line Amazon's net received when the answer's vendorTopLineNetReceived is 1, what the vendor invoiced Amazon when it is 0), 'purchase-orders' = Amazon's purchase orders and receipts, 'stock' = the stock at Amazon. A memo line that reads beside the P&L carries group, the chapter it belongs to ('Tax position': the tax collected from customers, what Amazon remitted itself, what is left for the seller to remit; never part of net sales or net profit).

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_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.

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?

The annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real behavioral value beyond that: it enumerates the fields each metric carries and, for 1P accounts, explains the conditional `channels`, `basis`, and `group` semantics — return-value context that matters because there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the remainder is a single sprawling sentence packed with nested colons, parentheticals, and conditional 1P-only detail. The information is useful and there is no output schema to hold it, yet the structure makes it hard to parse on a first read.

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 only a trivial input, the description correctly takes on the burden of describing what comes back, including the conditional fields for Vendor Central accounts. It omits nothing critical, though it could have noted whether the list is paginated or stable in size.

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?

The tool has one optional parameter whose schema description coverage is 100%, so the schema already fully documents the `reason` field. The description adds nothing about it, which is acceptable given the high coverage, but it means this dimension is carried entirely by 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?

The first sentence states a specific verb and resource plus the returned fields: 'List the metrics Nova can report (key, label, unit type, whether higher is better).' It also implicitly differentiates itself from siblings like describe_metric and query_metrics by positioning itself as the discovery step before those calls.

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?

'Call this first to discover valid metric keys for the other tools' gives explicit ordering guidance and names the downstream tools that depend on it. It does not explicitly exclude the closest sibling, describe_metric, or say when this is unnecessary, so it stops short of full when/when-not coverage.

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.