Version Packages - #41
Merged
Merged
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@iqai/mcp-debank@2.2.0
Minor Changes
304039f: Fetch whale NFT holdings by fanning out per-chain instead of the slow server-side aggregate.
getUserAllNftListpreviously called DeBank's/user/all_nft_list, which aggregates across every chain server-side and takes 10–20 s for active wallets — routinely timing out to nothing for whales (e.g. vitalik.eth). It now discovers the wallet's used chains (used_chain_list) and fans out the fast per-chain/user/nft_listcalls in parallel with bounded concurrency (8), so wall-clock is ≈ (chains / 8) × ~1.5 s.The method also degrades gracefully instead of failing all-or-nothing: a chain that errors or is too slow is dropped and reported, and the method enforces its own soft deadline (~75% of the call's timeout budget) so it returns the chains that landed before the client's hard abort fires — partial-on-timeout, mirroring the result-size-budget philosophy.
Return-shape change (guest-facing):
getUserAllNftListnow resolves to{ nfts, chains, partial, chains_skipped }instead of a bareUserNFT[]. Readresult.nftsfor the holdings (each NFT is stamped with itschain);partial: truewithchains_skippednames the chains to retry (narrow viachain_ids, or usegetUserNftListper chain). The tool description, cookbook, and instructions are updated accordingly.Patch Changes
ca6d059: Bound the
executeresult size so whale-wallet queries can't overflow the consuming model's context window.The
executetool serialized the guestrun()return value with no size limit and returned it verbatim to the MCP client. For large wallets (e.g. vitalik.eth), whole-portfolio queries — "all token holdings across all chains", "all NFT holdings", "all approvals on Ethereum" — produced payloads of ~500k tokens, which overflowed the consuming agent's context window before the summarizing model call could even run.There is now a generic size budget enforced at the result boundary (
DEBANK_MCP_EXECUTE_RESULT_BUDGET_CHARS, default 200,000 chars ≈ 50k tokens). When a result exceeds it, the envelope metadata (ok/error/log_lines/err_lines) is kept intact and the bulkresultis truncated — arrays keep the first N elements, objects trim their largest arrays, strings keep a prefix — with a structured_truncated: { shown, total, reason, hint }signal attached so the consumer can answer "showing top N of M — refine to see more" instead of crashing. Results under budget are returned byte-for-byte unchanged.