lossy-conversion
Does this value survive conversion to another numeric or spreadsheet type? Range, precision, leading zeros, E notation — Takes raw JSON literals (as written, so 9007199254740993, 1e400, -0, "007" and 0.10 are judged on their digits, not on a parsed double) and target types (binary64, binary32, int8..int64, uint8..uint64, PostgreSQL numeric(p,s), Arrow decimal128/decimal256, Parquet decimal, Excel cell, pandas int64) and reports for each pair whether the value is exact, lossy (rounded, truncated, leading zeros or sig
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "lossy-conversion"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pairs | No | Identifier or text values before and after a round trip through another system. | |
| samples | No | Raw JSON scalar literals exactly as written, e.g. 9007199254740993, "007", 1e400, 0.10, null. | |
| targets | No | Target types: float64, float32, int8, int16, int32, int64, uint8, uint16, uint32, uint64, numeric(p,s), decimal128(p,s), decimal256(p,s), parquet-decimal(p,s), excel-number, pandas-int64. |