Skip to main content
Glama

Amazon Seller MCP Server — AgentXray

Account health and open problems

get_account_health
Read-onlyIdempotent

Account health for each connected Amazon seller account: Amazon's own Account Health rating and account status, every problem the latest check found (with the SKUs it touches and what to do), and unacknowledged alerts of the last 14 days. Use it for 'is my account healthy', 'am I at risk of suspension', 'any policy problems'. Its narrative is the answer.

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": "get_account_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds real behavior beyond that: the data is a snapshot from 'the latest check', alerts are bounded to a 14-day window, and the `narrative` field is flagged as the primary answer field — valuable given 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.

Conciseness5/5

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

Front-loaded with the resource and its contents, then usage examples, then a one-clause pointer to the answer field. Every sentence carries information; nothing is repeated from the annotations or title.

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 does the work of naming the key return fields (rating, status, problems with SKUs, alerts, narrative). It is largely complete, though it leaves the shape of the problems and narrative payloads and the freshness/latency of 'the latest check' unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly implies no scoping inputs are needed, though it does not explicitly say the result spans all accounts at once.

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 concrete resource (account health for each connected Amazon seller account) and enumerates exactly what comes back: Amazon's own AHR rating, account status, every problem from the latest check with affected SKUs, and 14-day unacknowledged alerts. This is distinguishable from siblings like get_listing_issues (single-problem listing scope) and daily_brief because it is framed as the account-level health verdict.

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 three concrete triggering questions ('is my account healthy', 'am I at risk of suspension', 'any policy problems'), which firmly anchors when to call it. It never names an alternative tool or an exclusion case (e.g., when to prefer get_listing_issues for a specific listing), so it stops short of a full routing rule.

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.

Resources