Several tool schemas (e.g. positions[].price, positions[].cost_basis, orders[].execution_price, orders[].limit_price, orders[].stop_price, and nested legs[] equivalents) declare format: "decimal" on numeric properties.
"decimal" is not a format keyword defined in JSON Schema (draft 2020-12 or earlier drafts). MCP clients using standard JSON Schema validators (e.g. ajv) log warnings like:
unknown format "decimal" ignored in schema at path "#/properties/positions/items/properties/price"
for every affected field, on every tool load — this is noisy in bare-terminal usage (e.g. claude mcp list) though it doesn't break functionality (the format constraint is just silently skipped).
Could these fields drop format: "decimal" (relying on "type": "number" alone), or use a custom vendor format registered with clients that support it? Happy to share full CLI output if useful.
Several tool schemas (e.g.
positions[].price,positions[].cost_basis,orders[].execution_price,orders[].limit_price,orders[].stop_price, and nestedlegs[]equivalents) declareformat: "decimal"on numeric properties."decimal"is not a format keyword defined in JSON Schema (draft 2020-12 or earlier drafts). MCP clients using standard JSON Schema validators (e.g. ajv) log warnings like:for every affected field, on every tool load — this is noisy in bare-terminal usage (e.g.
claude mcp list) though it doesn't break functionality (the format constraint is just silently skipped).Could these fields drop
format: "decimal"(relying on"type": "number"alone), or use a custom vendor format registered with clients that support it? Happy to share full CLI output if useful.