> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fau.run/agent-docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Structured tools

> Travel, orders, and bills — fields only.

Need `structured_read` and the matching category on the grant. Success payloads are
JSON inside MCP content text.

## `get_upcoming_travel`

```json theme={null}
{ "days": 90 }
```

`days` optional (1–365, default 90).

Success:

```json theme={null}
{
  "trips": [
    {
      "kind": "flight",
      "starts_at": 1760000000,
      "from": "SFO",
      "to": "JFK",
      "reference": "…",
      "provider": "…",
      "seat": "…",
      "flight": "UA123",
      "thread_ref": "t_…"
    }
  ]
}
```

At most \~20 trips. Use `thread_ref` later with `get_excerpt` if needed.

## `order_status`

```json theme={null}
{ "merchant": "amazon" }
```

`merchant` required (≤ 80 chars).

Success: `{"orders":[…]}` with fields such as `merchant`, `status`, `order_id`,
`tracking`, `carrier`, `eta`, `amount`, `currency`, `thread_ref` (max \~20).

## `bills_due`

```json theme={null}
{ "before": 1760000000 }
```

`before` optional Unix timestamp; default \~30 days ahead.

Success: `{"bills":[…]}` with `biller`, `kind`, `due_at`, `amount`, `currency`,
`status`, `thread_ref` (max \~20).

## When to use `ask` instead

If intent does not map onto these schemas, call `ask` with one narrow question.
