Summary
The evolver_publish_asset MCP tool describes the obsolete queued-mailbox workflow, while current stable Evolver v1.92.1 publishes synchronously and returns the final result in the same request.
Plugin baseline: 3048fb73910a0a8944f74fb2e70abd5752a60b2f.
Contract mismatch
The tool description in mcp/evolver-proxy.mjs:172-194 says:
Queued locally and synced by the Proxy in the background; poll asset_submit_result ...
Current v1.92.1 behavior is different:
EvoMap/evolver/src/proxy/server/routes.js:113-125 awaits assetPublish and returns its result synchronously.EvoMap/evolver/src/proxy/index.js:901-925 publishes assets through /a2a/publish and returns {published, total, results}.EvoMap/evolver/test/proxyServer.test.js:175-185 explicitly asserts that /asset/submit no longer returns a queued message id.
Upstream source: https://github.com/EvoMap/evolver/blob/55f0ec73ff9192c54ecb932a1695c048e15518cf/src/proxy/server/routes.js#L113-L125
Actual impact
Publishing itself can succeed and the final Hub response is already returned to the MCP caller, but the agent is instructed to ignore that completion model and poll for an asset_submit_result that this path no longer creates. This can lead to empty polling and incorrect "still waiting" reports.
Expected result
The tool description should tell the agent to inspect the immediate {published, total, results} response. If compatibility with older runtimes is required, branch the guidance based on the returned shape rather than always requiring mailbox polling.
Summary
The
evolver_publish_assetMCP tool describes the obsolete queued-mailbox workflow, while current stable Evolver v1.92.1 publishes synchronously and returns the final result in the same request.Plugin baseline:
3048fb73910a0a8944f74fb2e70abd5752a60b2f.Contract mismatch
The tool description in
mcp/evolver-proxy.mjs:172-194says:Current v1.92.1 behavior is different:
EvoMap/evolver/src/proxy/server/routes.js:113-125awaitsassetPublishand returns its result synchronously.EvoMap/evolver/src/proxy/index.js:901-925publishes assets through/a2a/publishand returns{published, total, results}.EvoMap/evolver/test/proxyServer.test.js:175-185explicitly asserts that/asset/submitno longer returns a queued message id.Upstream source: https://github.com/EvoMap/evolver/blob/55f0ec73ff9192c54ecb932a1695c048e15518cf/src/proxy/server/routes.js#L113-L125
Actual impact
Publishing itself can succeed and the final Hub response is already returned to the MCP caller, but the agent is instructed to ignore that completion model and poll for an
asset_submit_resultthat this path no longer creates. This can lead to empty polling and incorrect "still waiting" reports.Expected result
The tool description should tell the agent to inspect the immediate
{published, total, results}response. If compatibility with older runtimes is required, branch the guidance based on the returned shape rather than always requiring mailbox polling.