mosquito / aiohttp-tiny-mcp / 36544516258

94%

master: 94%

Pull #3

github

Keep null valid in legacy-simplified schemas

simplify_legacy_schema removed the null branch of a union and published
the remaining branch alone. A nullable field was therefore advertised as
non-nullable, and a client that validates structuredContent rejected
every result that carried a null:

  task_add -> "closed_at": {"type": "integer"}, "snippet": {"type": "string"}
  result   -> "closed_at": null, "snippet": null
  client   -> data/closed_at must be integer, data/snippet must be string

Declare null in the collapsed branch instead: "type" becomes a list that
includes "null", and a nullable enum gains null among its choices. Both
forms are valid in draft-07, which the legacy revisions use. A branch
that cannot accept null, such as a const, is refused as before, so the
tool is hidden rather than published with a schema that rejects null.

Update the revisions reference, which described the lossy behaviour, and
add regression tests that validate null-bearing payloads against the
simplified schema.

16 of 19 new or added lines in 1 file covered. (84.21%)

6039 of 6398 relevant lines covered (94.39%)

0.94 hits per line