Skip to main content
Glama
Sign In
amazon-seller-mcp

amazon-seller-mcp

by agentxray-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Profit and loss from an Amazon settlement report

read_settlement_report
Read-only

Reads Amazon settlement reports from your disk to show exact sales, refunds, fees, net and per-SKU profit. Use it to verify what Amazon actually paid without uploading files.

Instructions

Reads an Amazon settlement report (the tab-separated flat file from Seller Central → Payments → Reports Repository) from this computer and returns what Amazon actually settled: sales, refunds, promotions, referral and FBA fees, storage, subscription, reimbursements and the net, plus units, orders, average price, FBA fee per unit and referral rate. With a unit cost it also returns profit after product cost. Amounts are exact to the cent. The file never leaves this machine.

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": {
      "path": "<path>"
    },
    "name": "read_settlement_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd date (YYYY-MM-DD, inclusive), compared with each line's posted date — the day Amazon moved the money. Omit for the whole report.
pathYesPath to the settlement report file (absolute, relative, or starting with ~).
startNoStart date (YYYY-MM-DD, inclusive), compared with each line's posted date — the day Amazon moved the money. Omit for the whole report.
cogs_per_unitNoOptional landed cost per unit in the report's currency, e.g. "7.40". Used to compute profit after product cost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false; the description earns extra credit by confirming locally that "the file never leaves this machine" and by promising cent-exact amounts. It also clarifies that the date filter is applied against the posted date, which is genuine behavioral detail. It stops short of describing failure behavior for malformed or missing files.

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?

The core capability and the file's provenance are front-loaded, and the local-privacy guarantee closes it out. The metrics enumeration in the middle sentence is long, though each listed item carries information about what the return contains.

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 carries the burden of explaining return values and does so thoroughly (sales, refunds, fees, net, units, orders, average price, referral rate, optional profit). For a four-parameter local parse tool that is nearly complete; only error/edge-case behavior is absent.

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 description coverage is 100%, so all four parameters including cogs_per_unit and the posted-date semantics of start/end are already documented. The description restates the cogs_per_unit outcome ("profit after product cost") without adding format, default, or edge-case meaning beyond the schema, so the baseline holds.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Reads an Amazon settlement report") and pins down the exact artifact: the tab-separated flat file from Seller Central → Payments → Reports Repository. It never names a sibling, so the agent gets no explicit contrast with settlement_profit_by_sku, which is presumably the per-SKU breakdown.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the description makes clear this is the tool for pulling settled amounts from a local file, and it explains the conditional branch "with a unit cost it also returns profit". There is no when-not guidance, no mention of when to reach for settlement_profit_by_sku instead, and no prerequisites (report must already be downloaded) called out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools