Skip to content
← Changelog
fixed

MCP write tools accept only the arguments they declare

From planned work to a release note The public record separates future intent from behavior that shipped on a stated date. Release record 01 Roadmap Intent 02 Product Shipped 03 Release note Dated From planned work to a release note The public record separates future intent from behavior that shipped on a stated date. Release record 01 Roadmap Intent 02 Product Shipped 03 Release note Dated
From planned work to a release note The public record separates future intent from behavior that shipped on a stated date.

Every MCP write tool now refuses an argument its schema does not declare (validation_error, with the offending keys in the message) instead of silently ignoring it. invoice_create never takes a settlement address: the invoice settles to your verified wallet for the buyer's network, and the preview now lists those wallets under settles_to. subscription_create declares its metadata argument in the schema.

This note records shipped behavior as of . Planned work remains on the public roadmap until release.