Fix inconsistency in task capabilities spec

Author: LucaButBoring

docs/specification/draft/basic/utilities/tasks.mdx

@@ -92,7 +92,7 @@ Clients declare if they support tasks, and if so, which client-side requests can
 
 During the initialization phase, both parties exchange their `tasks` capabilities to establish which operations support task-based execution. Requestors **MUST** only augment requests with task metadata if the corresponding capability has been declared by the receiver.
 
-For example, if a server's capabilities include `tasks.requests.tools.call: true`, then clients may augment `tools/call` requests with task metadata. If a client's capabilities include `tasks.requests.sampling.createMessage: true`, then servers may augment `sampling/createMessage` requests with task metadata.
+For example, if a server's capabilities include `tasks.requests.tools.call: {}`, then clients may augment `tools/call` requests with task metadata. If a client's capabilities include `tasks.requests.sampling.createMessage: {}`, then servers may augment `sampling/createMessage` requests with task metadata.
 
 If `capabilities.tasks` is not defined, the peer **MUST NOT** attempt to create tasks during requests.