Skip to main content
Glama
Sign In

SKU.io

by io.sku
OverviewDiscussionsAdmin

Get Amazon reimbursement cases

get_reimbursement_cases
Read-onlyIdempotent

Lists Amazon FBA reimbursement cases with status, category, amount and filing deadline, or returns one case in full when id is given.

Input Schema

NameRequiredDescriptionDefault
idNoOne case's id, to return that case in full instead of a list.
pageNo
per_pageNoPage size (default 10, max 100).
filter_searchNoCase id, SKU, ASIN, order, shipment or Amazon case id.
filter_categoryNoComma-separated categories, e.g. warehouse_lost.
filter_ui_groupNoComma-separated stages: found, ready, waiting, paid, auto_paid, closed.
filter_due_within_daysNoClaim window closes within N days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedInput schema / properties / filter[category]
      Removed value: -{
-  "description": "Comma-separated categories, e.g. warehouse_lost.",
-  "type": "string"
-}
    • removedInput schema / properties / filter[due_within_days]
      Removed value: -{
-  "description": "Claim window closes within N days.",
-  "type": "integer"
-}
    • removedInput schema / properties / filter[search]
      Removed value: -{
-  "description": "Case id, SKU, ASIN, order, shipment or Amazon case id.",
-  "type": "string"
-}
    • removedInput schema / properties / filter[ui_group]
      Removed value: -{
-  "description": "Comma-separated stages: found, ready, waiting, paid, auto_paid, closed.",
-  "type": "string"
-}
    • addedInput schema / properties / filter_category
      Added value: +{
+  "description": "Comma-separated categories, e.g. warehouse_lost.",
+  "type": "string"
+}
    • addedInput schema / properties / filter_due_within_days
      Added value: +{
+  "description": "Claim window closes within N days.",
+  "type": "integer"
+}
    • addedInput schema / properties / filter_search
      Added value: +{
+  "description": "Case id, SKU, ASIN, order, shipment or Amazon case id.",
+  "type": "string"
+}
    • addedInput schema / properties / filter_ui_group
      Added value: +{
+  "description": "Comma-separated stages: found, ready, waiting, paid, auto_paid, closed.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only that the list includes a filing deadline (a time-sensitivity signal), but says nothing about result ordering, pagination totals, or what 'in full' includes beyond the listed fields.

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?

A single front-loaded sentence with zero filler; the list mode is stated first and the id-mode exception follows. Nothing is repeated from annotations or schema.

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 seven parameters, no output schema and no enum constraints, the description usefully substitutes by enumerating the returned fields (status, category, amount, deadline). It stops short of explaining pagination behavior or result ordering, which matters for a paged list endpoint whose page/per_page semantics live only in the schema.

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 86%, so nearly every parameter is already documented in the schema, and the description only reinforces the id mode. It adds no meaning about how filter_search or filter_due_within_days combine, which is the one gap the schema leaves open (no filtering semantics are disclosed).

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?

Names a specific verb and resource (lists Amazon FBA reimbursement cases) and enumerates the returned fields, plus explains the alternate single-record mode keyed on id. It does not name or contrast any sibling tool, but none of the listed siblings covers reimbursements, so disambiguation is largely unnecessary.

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?

The clause 'returns one case in full when id is given' implicitly tells the agent how to switch modes, but there is no explicit guidance on when to prefer this tool over adjacent reporting tools, and no stated prerequisites or exclusions. Usage has to be inferred from the purpose statement.

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

All SKU.io toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources