chore(deps): bump @toon-format/toon from 1.0.0 to 2.0.1 #30
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…25-06-18 - Updated Server header from 1.1.0 to 1.2.0 - Updated /health endpoint version and protocol - Updated /info endpoint version and protocol - Updated /authorize endpoint version - Updated GET /mcp endpoint version and protocol - Updated 404 handler protocol version Ensures complete version consistency across all HTTP endpoints and responses.
- Added additionalProperties: false to warmup object - Added additionalProperties: false to warmup.advanced object This resolves MCP schema validation errors in strict clients like Augment and Cursor that were causing tools to be disabled with 'validation errors' message.
JSON Schema validation errors were caused by 'additionalProperties: true' which is not valid in strict validators. Fixed by: - Removed additionalProperties: true from campaign_schedule object - Removed additionalProperties: true from campaign_schedule.schedules items - Removed additionalProperties: true from sequences items - Removed additionalProperties: true from auto_variant_select object - Removed additionalProperties: true from all custom_variables objects (3 instances) - Added additionalProperties: false to reply_to_email body object When arbitrary properties are needed, omitting additionalProperties entirely is the correct approach per JSON Schema spec, not setting it to true. This resolves 'MCP server has validation errors' in Augment and Cursor.
Implements TOON (Token-Oriented Object Notation) encoding for tool responses, providing 30-60% token reduction for uniform tabular data while maintaining full MCP protocol compatibility. Changes: - Added @toon-format/toon dependency (v1.0.0) - Created response-formatter utility with automatic TOON/JSON selection - Implemented TOON encoding for list_accounts (proof of concept) - Added TOON_IMPLEMENTATION.md documentation Benefits: - 30-60% token savings for list operations (accounts, campaigns, leads) - Better context window efficiency for large datasets - LLM-friendly structure with explicit array lengths and field headers - Automatic fallback to JSON for non-uniform data - No breaking changes to MCP protocol (text content is valid) Next steps: - Roll out to list_campaigns, list_leads, list_emails - Add analytics tools (time-series data is perfect for TOON) - Monitor token savings in production
The initial implementation was too strict - required exact same keys in all objects.
Real-world Instantly API data has optional fields (warmup, daily_limit, etc).
Changes:
- Relaxed uniformity check to allow optional fields (50% key overlap threshold)
- Added data normalization (fills missing fields with null before TOON encoding)
- Allow empty objects like warmup: {} (common in Instantly API)
- Fixed TypeScript type error for Object.keys()
This should now properly detect and encode account/campaign/lead arrays as TOON,
even when objects have different optional fields.
TOON library was using YAML-style list format for non-uniform data,
which is actually WORSE for tokens than JSON. Now we detect this and
automatically fall back to JSON.
Detection: Check if TOON output contains '{' and '}:' (tabular format markers).
If not, it used YAML format (starts with '- '), so we use JSON instead.
This ensures we only use TOON when it actually provides token savings.
Applied createMCPResponse() to: - list_campaigns - get_campaign - get_campaign_analytics - get_daily_campaign_analytics - get_warmup_analytics - list_emails - list_leads - get_lead - list_lead_lists All tools tested successfully. Smart fallback working correctly - returns JSON for non-uniform data, will use TOON for uniform data. This ensures maximum token efficiency while maintaining compatibility.
- Fixed JSON Schema validation error in create_campaign tool definition - Removed 'additionalProperties: true' which is invalid in strict validators (Augment, Cursor) - This was preventing create_campaign from appearing in MCP client tool lists - All 36 tools now validate correctly and load in MCP clients Issue: create_campaign tool was not appearing in Augment/Cursor Root cause: Invalid JSON Schema - additionalProperties: true not allowed Solution: Remove additionalProperties property (defaults to allowing additional properties) Tested: Tool validation passes, all 36 tools present
…and description compaction BREAKING CHANGES: - Tool count reduced from 36 to 31 (consolidated duplicates) - get_account_details + get_account_info -> get_account (with backward compat) - pause/resume/warmup/vitals tools -> manage_account_state (with backward compat) Optimizations: - Updated MCP SDK from 1.15.1 to 1.22.0 - Implemented tool pagination (MCP 2025-06-18 spec) - Compacted all tool descriptions for ~40% token reduction - Added tool annotations (readOnlyHint, destructiveHint, confirmationRequiredHint) - Consolidated 5 account state tools into manage_account_state Backward Compatibility: - Legacy tool names still work via internal routing - Old SDK clients will receive all tools (pagination optional) Files Changed: - package.json: SDK upgrade - src/config/tool-pagination.ts: New pagination utility - src/handlers/mcp-handlers.ts: Pagination support in tools/list - src/handlers/tool-executor.ts: Consolidated tool handlers - src/tools/*.ts: Compacted descriptions + annotations
Bumps [@toon-format/toon](https://github.com/toon-format/toon) from 1.0.0 to 2.0.1. - [Release notes](https://github.com/toon-format/toon/releases) - [Commits](toon-format/toon@v1.0.0...v2.0.1) --- updated-dependencies: - dependency-name: "@toon-format/toon" dependency-version: 2.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/toon-format/toon-2.0.1
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps @toon-format/toon from 1.0.0 to 2.0.1.
Release notes
Sourced from
@toon-format/toon's releases.Commits
690e402chore: release v2.0.14190d4cdocs(readme): use themed badges (#227)e35d8f7chore: move readme to packages/toon/README.md and symlink in the… (#228)f882cb1docs: update spec page to match latest version and sectionsb9e3593docs(benchmarks): improve clarity of efficiency ranking metricsfaf3f8ddocs: update implementation status for Java, Python, and Rust5310e8achore: release v2.0.07e6e180chore: upgrade depsa07d633docs: move JToon to official implementation9a61254docs: update benchmarks for v3 list item syntaxDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)