amazon-orders-mcp

Overview Schema Source Related Servers Discussions Admin

check_session

Read-only

Check with Amazon whether the user's saved sessions still work: on site, or else on their default site and every other Amazon site they have a saved session for. Also says which site is the default.

Instructions

Input Schema

Name	Required	Description	Default
`site`	No	The Amazon site to check, e.g. `amazon.de`. By default, the default site and every other site with a saved session are checked.

Output Schema

Name	Required	Description
`site`	Yes	The Amazon site, as `site` accepts it.
`error`	No	Why the session couldn't be checked, if it couldn't. `signed_in` is null then.
`sites`	Yes	Every site checked: the one asked about, or else the default site and every other site with a saved session.
`default`	Yes	Whether it's the user's default site, which tools read when they aren't given `site`.
`sign_in`	No	What to do to sign in, if the user isn't.
`signed_in`	Yes	Whether Amazon still accepts the user's saved session for the site. If Amazon answers the check with an error page, a saved session is assumed to still work. Null if the session couldn't be checked at all.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv1.4.2Oct 22, 2026

addedInput schema / properties / site

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The Amazon site to check, e.g. `amazon.de`. By default, the default site and every other site with a saved session are checked.",
+  "title": "Site"
+}

addedOutput schema / $defs

Added value: +{
+  "SiteSessionStatus": {
+    "description": "The user's session status on an Amazon site.",
+    "properties": {
+      "default": {
+        "description": "Whether it's the user's default site, which tools read when they aren't given `site`.",
+        "title": "Default",
+        "type": "boolean"
+      },
+      "error": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Why the session couldn't be checked, if it couldn't. `signed_in` is null then.",
+        "title": "Error"
+      },
+      "sign_in": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "What to do to sign in, if the user isn't.",
+        "title": "Sign In"
+      },
+      "signed_in": {
+        "anyOf": [
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Whether Amazon still accepts the user's saved session for the site. If Amazon answers the check with an error page, a saved session is assumed to still work. Null if the session couldn't be checked at all.",
+        "title": "Signed In"
+      },
+      "site": {
+        "description": "The Amazon site, as `site` accepts it.",
+        "title": "Site",
+        "type": "string"
+      }
+    },
+    "required": [
+      "signed_in",
+      "site",
+      "default"
+    ],
+    "title": "SiteSessionStatus",
+    "type": "object"
+  }
+}

changedOutput schema / description

Previous value: -"The user's Amazon session status, returned by the ``check_session`` tool."New value: +"The user's Amazon session status, returned by the ``check_session`` and ``sign_in`` tools: for the site asked\nabout, or else the default site, and for every site checked."

addedOutput schema / properties / default

Added value: +{
+  "description": "Whether it's the user's default site, which tools read when they aren't given `site`.",
+  "title": "Default",
+  "type": "boolean"
+}

addedOutput schema / properties / error

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Why the session couldn't be checked, if it couldn't. `signed_in` is null then.",
+  "title": "Error"
+}

addedOutput schema / properties / signed_in / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / signed_in / description

Previous value: -"Whether Amazon still accepts the user's saved session. If Amazon couldn't be reached to check, a saved session is assumed to still work."New value: +"Whether Amazon still accepts the user's saved session for the site. If Amazon answers the check with an error page, a saved session is assumed to still work. Null if the session couldn't be checked at all."

removedOutput schema / properties / signed_in / type
```
Removed value: -"boolean"
```

changedOutput schema / properties / site / description

Previous value: -"The Amazon site the server is set to read."New value: +"The Amazon site, as `site` accepts it."

addedOutput schema / properties / sites

Added value: +{
+  "description": "Every site checked: the one asked about, or else the default site and every other site with a saved session.",
+  "items": {
+    "$ref": "#/$defs/SiteSessionStatus"
+  },
+  "title": "Sites",
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "signed_in",
-  "site"
-]New value: +[
+  "signed_in",
+  "site",
+  "default",
+  "sites"
+]

First observedv1.2.0Oct 18, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint=true) and network reach (openWorldHint=true). The description adds genuine behavioral detail beyond them: the fan-out scope of sites checked when `site` is omitted, and the side-effect-free extra output of which site is the default.

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, both load-bearing: the first defines the check and its fallback scope, the second adds the default-site reporting. Nothing is padded and the primary action is front-loaded.

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 a single optional parameter, full schema coverage, annotations, and an output schema, the description covers everything an agent needs to invoke it correctly. The only unstated piece is what the tool does when a session is invalid, which the output schema can reasonably carry.

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 100%, and the description largely restates the schema's own wording for `site` (including the fallback-to-default-semantics). It adds no new syntax or format detail beyond the schema's `amazon.de` example, so the baseline 3 applies.

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: check with Amazon whether the user's saved sessions are still valid, and additionally report the default site. That is clearly distinct from the mutation sibling sign_in, but the description never names or contrasts an alternative tool, so it stops short of the top band.

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?

It explains the branching behavior well (check `site` if given, otherwise the default site plus every site with a saved session), which is effectively guidance on how to call it. But there is no explicit when-to-use/when-not-to-use framing, nor any pointer to sign_in for the case where no session exists.

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

Deploy Server