list_ordersYour owner's orders, newest first, a page at a time: order_id, item, amount, status and created_at (get_order for one in full). Pass next_before as before for the next page.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many (default 20). | |
| before | No | next_before of the page before. | |
| passport_token | No | Your amp_ token, only if you have no app sign-in and cannot send a header. |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "before": "ord_exampleexampleexample2",
+ "limit": 10
+ }
+]Input schema / properties / passport_token / descriptionPrevious value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."Input schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Input schema / properties / passport_token / descriptionPrevious value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."Input schema / properties / passport_token / maxLengthAdded value: +200Input schema / properties / passport_token / patternRemoved value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly=true, destructive=false and openWorld=false, so the safety profile is covered. The description adds real value by disclosing the sort order (newest first) and the cursor-based pagination mechanic, but says nothing about default/maximum page size behavior, empty-result handling, or scope filtering beyond 'your owner's'.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the resource and ordering, then the fields, then the sibling pointer and paging instruction. No filler and nothing repeated from the schema or annotations.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the field list (order_id, item, amount, status, created_at) usefully describes the return shape, and pagination is explained. Auth details are left to the passport_token schema entry, which is reasonable; only edge-case behavior (empty list, end of pages) is unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3; the description goes slightly further by explaining the relationship between the returned next_before and the before parameter, which is the non-obvious part of paginating. It still leaves limit and passport_token entirely to the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource (owner's orders), its ordering (newest first), its paging model, and the exact fields returned, so the agent knows precisely what comes back. It also names the sibling get_order as the single-record alternative, so the two are distinguishable without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes single-record lookups to get_order ('get_order for one in full') and explains how to continue paging via next_before. That is clear context plus a named alternative, though it doesn't state preconditions such as requiring owner scope when no orders exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.