REVIEWABLE VENDOR IMPORTS
Preserve leading-zero IDs and exact decimals
Keep identifiers as text and avoid binary floating-point conversions in vendor imports.
An identifier is not an amount
customer_id,credit_limit 000401,123456789012.123456789 000402,2500.05
The reviewed target keeps customer_id as a string and credit_limit as a number. 000401 stays a string; this beta refuses leading-zero identifier-to-number casts.
Use exact values throughout the workflow
JSON numbers are parsed as integers or Decimal values. Target constraints and mapping arguments travel as strict JSON strings so they do not pass through JavaScript floating-point values. A supported decimal-text-to-number cast preserves the exact mathematical value.
{"customer_id":"000401","credit_limit":123456789012.123456789}
For the Python SDK, parse exact numeric data with mcp_products.schema_mapper.serialization.loads, and serialize with its dumps. Converting a Decimal into a float elsewhere in your application can still lose precision.
Check the actual contract
Missing, null and empty string are distinct. Numeric text uses invariant decimal notation; currency symbols, grouped digits and decimal commas are unsupported. Every produced record is checked against the required fields, nullability, enums and inclusive numeric bounds you supplied.
The working example on the homepage uses these exact values. Preview and validation are free; the approved artifact costs $9 once. These properties demonstrate supported behavior, not universal safety for every financial workflow.