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

amazon-seller-mcp

by agentxray-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Find settlement reports in a folder

list_settlement_reports
Read-only

Lists Amazon settlement reports in a folder, showing settlement ID, period, deposit date, currency, and deposit total for each, newest first, while skipping non-report files.

Instructions

Lists the Amazon settlement reports in a folder on this computer (for example your Downloads folder), with settlement id, period, deposit date, currency and deposit total for each, newest period first. Files that are not settlement reports are skipped.

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": {
      "directory": "<directory>"
    },
    "name": "list_settlement_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryYesFolder to look in (absolute, relative, or starting with ~).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a safe local read. Beyond that it discloses real behavior: the local-filesystem scope, the exact result ordering ('newest period first'), and that unrelated files are silently skipped. It does not cover failure behavior for a missing/inaccessible folder or how large result sets are handled.

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

Conciseness5/5

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

Two sentences, no filler, with the core action and returned fields front-loaded and the edge-case filtering rule trailing. Every clause carries information the agent needs.

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

Completeness5/5

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

This is a simple single-parameter read tool with no output schema, so the description must describe the return shape, and it does so by enumerating the five fields plus their ordering. Combined with the skip-behavior note and the local-scope statement, nothing essential for correct invocation is missing.

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?

With a single parameter and 100% schema description coverage ('absolute, relative, or starting with ~'), the schema already carries the semantics. The description only reinforces that the argument is a local folder path ('a folder on this computer, for example your Downloads folder'), which is mild added value over the schema.

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?

The description gives a specific verb and resource ('Lists the Amazon settlement reports in a folder') plus the exact fields returned (settlement id, period, deposit date, currency, deposit total), so the agent knows this is a metadata-discovery tool rather than a content reader. It never explicitly names the sibling read_settlement_report as the follow-up for reading a report, so sibling routing is only implicit.

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?

Usage context is clear: point it at a folder on the local machine, with 'your Downloads folder' given as a concrete example, and it explains that non-settlement files are skipped rather than erroring. There is no explicit statement of when to prefer this over read_settlement_report or settlement_profit_by_sku, so a small inference is left to the agent.

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