faxforagents-mcp 0.5.3 → 0.5.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +49 -0
- package/README.md +5 -3
- package/dist/index.js +1192 -107
- package/llms-install.md +1 -1
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,54 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.5.5 (2026-11-15)
|
|
4
|
+
|
|
5
|
+
The stdio server follows the hosted server at API 1.20.9.
|
|
6
|
+
|
|
7
|
+
A refusal names the tool's argument, as the hosted server's has since 1.20.8. It named the REST API's field before.
|
|
8
|
+
|
|
9
|
+
- `quote_fax`: `from_number`, where the API says `from`.
|
|
10
|
+
- `request_card_payment`: `cover_from_name`, where the API says `sender_name`.
|
|
11
|
+
- `request_human_review`: `fax_id`, where the API says `fax_job_id`.
|
|
12
|
+
|
|
13
|
+
The name changes in `details.field`, in `details.fields` and in the `loc` of a validation error. A message that starts with the field changes too: "from must be E.164" from `quote_fax` reads "from_number must be E.164".
|
|
14
|
+
The `not_found` of a sender number that is not yours carries `details.field: "from_number"`. It carried `from` before.
|
|
15
|
+
A tool with no renamed argument passes the API's words on as they are.
|
|
16
|
+
|
|
17
|
+
The card of a one-time order is held, not authorized. `get_card_payment_status`, the guide section `one_time` and the description of `request_card_payment` say so.
|
|
18
|
+
`get_card_payment_status` and the description of `request_card_payment` also state the payment rule of API 1.20.9. A failed fax costs nothing, and a fax that stops part way costs the price of the pages that arrive.
|
|
19
|
+
|
|
20
|
+
The guide says a one-page fax to the sandbox number `+15550000003` fails with `partial_delivery`. Its `errors` section says `details.field` names the tool's argument. Its `policies` section says to ask a person only when `approval_required` is true.
|
|
21
|
+
|
|
22
|
+
The output schemas name the fields the API added at 1.20.8.
|
|
23
|
+
|
|
24
|
+
- `quote_fax`: `quote.pricing`, and `quote.policy_evaluation` as the policy verdict with its `usage`.
|
|
25
|
+
- `send_approved_fax`, `get_fax_status`, `list_faxes`, `cancel_fax` and `get_card_payment_status`: `approval_id`, `policy_version_id` and `route_paused` on the fax.
|
|
26
|
+
- New descriptions for `details`, for a document's `converted_from` and `received`, and for `amount_micro` of a received fax and of a card order.
|
|
27
|
+
|
|
28
|
+
0.5.4 differed from the hosted tool list in 55 places, 54 of them in the output schemas. 0.5.5 differs in none.
|
|
29
|
+
The tool list was taken from the hosted server's `tools/list` on 2026-11-15, when it reported version 1.20.9.
|
|
30
|
+
The list equals the definitions `scripts/import-hosted.py` imported from the product source at v1.20.9.
|
|
31
|
+
`test/argument-names.mjs` checks eight refusals over stdio. `test/tools-output.mjs` gives its denied quote the whole verdict the API sends, with `managed` and `denials`.
|
|
32
|
+
|
|
33
|
+
## 0.5.4 (2026-11-15)
|
|
34
|
+
|
|
35
|
+
The stdio server follows the hosted server at API 1.20.6. Tool names, inputs, descriptions and the guide did not change. The output schemas did.
|
|
36
|
+
|
|
37
|
+
The output schemas name the fields the API added at 1.20.6. The handlers pass the API's objects through, so the fields reach a client as they are.
|
|
38
|
+
|
|
39
|
+
- `get_fax_balance`: `balance.held_jobs`, the fax jobs whose hold is still in place.
|
|
40
|
+
- `quote_fax`: `quote.route_paused`, true while an operator has paused sends on the route.
|
|
41
|
+
- `prepare_fax` and `get_fax_document`: `document.converted_from`, the name of an image that became the PDF, and `document.received`, the received fax the document came from.
|
|
42
|
+
- `request_human_review` and `get_review_status`: `document`, `requested_by_name` and `decided_by_name` on the review request.
|
|
43
|
+
- `get_fax_capabilities`: `default_scopes` and `admin_scopes`.
|
|
44
|
+
- `send_approved_fax`, `get_fax_status`, `list_faxes`, `cancel_fax` and `get_card_payment_status`: six receipt fields of a one-time order on `one_time`.
|
|
45
|
+
|
|
46
|
+
Every new field is optional. 0.5.3 differed from the hosted tool list in 48 places of the output schemas, and 0.5.4 differs in none.
|
|
47
|
+
|
|
48
|
+
The tool list was taken from the hosted server's `tools/list` on 2026-11-15, when it reported version 1.20.7.
|
|
49
|
+
The list equals the definitions `scripts/import-hosted.py` imported from the product source at v1.20.6.
|
|
50
|
+
`llms-install.md` writes the hosted address as `https://mcp.faxforagents.com/mcp/` and no longer says to keep the trailing slash. Both forms answer the same.
|
|
51
|
+
|
|
3
52
|
## 0.5.3 (2026-11-14)
|
|
4
53
|
|
|
5
54
|
The stdio server follows the hosted server at API 1.20.5.
|
package/README.md
CHANGED
|
@@ -247,8 +247,8 @@ before the person pays.
|
|
|
247
247
|
Paying by card does not replace approval. The tool takes the same `approval_id` as `send_approved_fax`,
|
|
248
248
|
or a delegated policy has to allow the send. `get_card_payment_status` reads the order: `next` is
|
|
249
249
|
`checkout`, `confirm`, `wait` or `done`, and once the fax was released the answer carries the fax and
|
|
250
|
-
the carrier's evidence. The card is
|
|
251
|
-
reports as arrived. Live keys only, United States and Canada. The guide section `one_time` has the
|
|
250
|
+
the carrier's evidence. The card is held at payment. A failed fax costs nothing, and a fax that stops
|
|
251
|
+
part way costs the price of the pages the carrier reports as arrived. Live keys only, United States and Canada. The guide section `one_time` has the
|
|
252
252
|
steps, and `going_live` says how to get from the sandbox to a real fax.
|
|
253
253
|
|
|
254
254
|
## Prices
|
|
@@ -279,9 +279,11 @@ An argument the tool does not list gets the same answer. The message names it an
|
|
|
279
279
|
The message names the argument, its expected type or ID format, and the correction to make.
|
|
280
280
|
Resource IDs require the correct prefix and exactly 32 lowercase hexadecimal characters.
|
|
281
281
|
Well-formed unknown IDs reach the REST API and return `not_found`.
|
|
282
|
+
A refusal from the REST API names the tool's argument, as the hosted server's does: `from_number` where the API says `from`.
|
|
283
|
+
This holds in `details.field`, `details.fields`, the `loc` of a validation error and a message that starts with the field. `test/argument-names.mjs` checks it.
|
|
282
284
|
Protocol errors, such as a non-object arguments container, remain JSON-RPC errors.
|
|
283
285
|
Tests use hosted responses recorded on 2026-11-02 and a local fake REST API. They need no hosted credentials.
|
|
284
|
-
The tool snapshot is the hosted server's `tools/list` of 2026-11-
|
|
286
|
+
The tool snapshot is the hosted server's `tools/list` of 2026-11-15 at API 1.20.9. Normal tests never contact the hosted server.
|
|
285
287
|
`test/hosted-unknown-arguments.json` holds what the hosted source answers for 20 calls with unknown arguments. `test/validation.mjs` compares each one.
|
|
286
288
|
The server does not start when a handler's inputs differ from the tool list. `test/inputs.mjs` calls every listed input over stdio. A wrong type has to be refused and the listed example accepted. An argument a tool does not list has to be refused by name.
|
|
287
289
|
To import definitions before deployment, run the following with the product checkout's Python environment.
|