@mondaydotcomorg/agent-toolkit 5.65.0 → 5.65.2
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 +15 -0
- package/dist/cjs/core/index.js +3 -2
- package/dist/cjs/core/index.js.map +1 -1
- package/dist/cjs/mcp/index.js +3 -2
- package/dist/cjs/mcp/index.js.map +1 -1
- package/dist/cjs/openai/index.js +3 -2
- package/dist/cjs/openai/index.js.map +1 -1
- package/dist/esm/core/index.js +3 -2
- package/dist/esm/core/index.js.map +1 -1
- package/dist/esm/mcp/index.js +3 -2
- package/dist/esm/mcp/index.js.map +1 -1
- package/dist/esm/openai/index.js +3 -2
- package/dist/esm/openai/index.js.map +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,20 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 5.65.1
|
|
4
|
+
|
|
5
|
+
### create_notification — report failures instead of swallowing them
|
|
6
|
+
|
|
7
|
+
`create_notification` caught every error and returned the plain string `Failed to send notification to user <id>` as its result. Because the MCP layer only marks a call as an error when the tool *throws*, that string was delivered as a **success** — callers could not distinguish a delivered notification from a failed one, and the underlying cause was discarded entirely.
|
|
8
|
+
|
|
9
|
+
- Errors now go through `rethrowWithContext(error, 'send notification to user <id>')`, the same path already used by `create_update` and `delete_update`. GraphQL failures surface their real messages plus `extensions.code` / `error_data`, and reach the client as `isError: true` with JSON `structuredContent`: `{ message, tool, status, errors: [{ code, message, path }] }`
|
|
10
|
+
- Added an empty-response guard — the API can return `create_notification: null` with no GraphQL error, which previously reported success. It now throws a `ToolValidationError` coded `EMPTY_API_RESPONSE` naming the likely cause: a `target_id` / `target_type` mismatch (`Post` expects an update/reply id, `Project` expects an item/board id)
|
|
11
|
+
- Success output is a JSON object with `notification_id`, `user_id`, `target_id`, `target_type`, and `text` (previously only `message`, `user_id`, `text`). The mutation now selects `id` so the created notification can be identified
|
|
12
|
+
- No input schema changes. Callers that treated the old failure string as a soft failure will now see a thrown error
|
|
13
|
+
|
|
14
|
+
### all_api_read — drop get_graphql_schema from the stated prerequisites
|
|
15
|
+
|
|
16
|
+
- `all_api_read` no longer names `get_graphql_schema` as a prerequisite, leaving `get_type_details` as the single lookup to call before crafting a query (and fixing the plural "tools" left behind by the removal). `all_api_write` and `all_monday_api` still name both tools
|
|
17
|
+
|
|
3
18
|
## 5.65.0
|
|
4
19
|
|
|
5
20
|
### Short, self-explaining first sentence for every monday tool description
|