link_work_items MCP tool uses array-form type in inputSchema, breaking some MCP clients

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Collaborate/take over this issue

Summary

The link_work_items tool's inputSchema declares work_items_ids.items with an array-form type:

"items": {"type": ["integer", "string"]}

This is valid JSON Schema but several MCP clients read type as a single string and either reject the tool or silently drop the constraint. Flagged by MCP Inspector.

Expected behavior

Use anyOf instead of the array form:

"items": {
  "anyOf": [{"type": "integer"}, {"type": "string"}]
}

This is equivalent semantically and compatible with all known MCP clients. It does not interact with additionalProperties: false on the parent object since it's inside items, not at the root schema level.

Other tools

Other MCP tools that accept mixed-type array items should be audited for the same pattern.