Problem
The get_schema tool truncates large schemas mid-content, cutting off at an arbitrary character limit. This causes incomplete data to be returned without a clear signal that truncation occurred — the response ends mid-word or mid-object with a note saying "Schema truncated. Use the property parameter to focus on specific sections."
This is misleading because:
- The truncation note implies using
property will help, but for schemas with large oneOf arrays, even targeted queries may still truncate.
- An AI assistant reading the truncated output may draw incorrect conclusions from the incomplete data (e.g., concluding a
oneOf branch doesn't exist when it was simply cut off).
Example
Fetching creative/preview-render.json truncates mid-way through the third oneOf branch (output_format: "both"). The first two branches (url, html) are returned fully, but the third is cut off mid-sentence.
Fetching creative/preview-creative-response.json truncates mid-way through the "batch" branch, hiding the existence of the "variant" branch entirely.
Expected behavior
Either:
- Return the full schema regardless of size, or
- If a size limit is unavoidable, truncate only at clean JSON boundaries (e.g., end of a complete
oneOf entry) and clearly indicate how many items were omitted (e.g., "Showing 2 of 3 oneOf branches")
Affected tool
get_schema (Addie tool)
Impact
Incomplete schema responses can cause incorrect conclusions about what is and isn't valid in the spec — a correctness issue, not just a UX issue.
Problem
The
get_schematool truncates large schemas mid-content, cutting off at an arbitrary character limit. This causes incomplete data to be returned without a clear signal that truncation occurred — the response ends mid-word or mid-object with a note saying "Schema truncated. Use thepropertyparameter to focus on specific sections."This is misleading because:
propertywill help, but for schemas with largeoneOfarrays, even targeted queries may still truncate.oneOfbranch doesn't exist when it was simply cut off).Example
Fetching
creative/preview-render.jsontruncates mid-way through the thirdoneOfbranch (output_format: "both"). The first two branches (url,html) are returned fully, but the third is cut off mid-sentence.Fetching
creative/preview-creative-response.jsontruncates mid-way through the "batch" branch, hiding the existence of the "variant" branch entirely.Expected behavior
Either:
oneOfentry) and clearly indicate how many items were omitted (e.g., "Showing 2 of 3 oneOf branches")Affected tool
get_schema(Addie tool)Impact
Incomplete schema responses can cause incorrect conclusions about what is and isn't valid in the spec — a correctness issue, not just a UX issue.