Get JSON SchemaBundle
Identifierhttps://schemas.sourcemeta.com/a2a/v0.2.3/schema.json
Base DialectDraft7
Dialecthttp://json-schema.org/draft-07/schema#
Health
79%
Size0.057895 MB
Loading schema...

This schema has 0 direct dependencies and 0 indirect dependencies.

This schema has 90 quality errors.

/definitions/APIKeySecurityScheme/properties/in/enumenum_with_type

Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types

/definitions/APIKeySecurityScheme/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/AgentCard/properties/capabilities/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/AgentCard/properties/provider/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/AgentExtension/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Artifact/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/CancelTaskRequest/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/CancelTaskRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/CancelTaskRequest/properties/params/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/CancelTaskSuccessResponse/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/CancelTaskSuccessResponse/properties/result/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/ContentTypeNotSupportedError/properties/code/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/DataPart/properties/data/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/DataPart/properties/kind/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/DataPart/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/FilePart/properties/kind/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/FilePart/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/GetTaskPushNotificationConfigRequest/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/GetTaskPushNotificationConfigRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/GetTaskPushNotificationConfigRequest/properties/params/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/GetTaskPushNotificationConfigSuccessResponse/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/GetTaskPushNotificationConfigSuccessResponse/properties/result/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/GetTaskRequest/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/GetTaskRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/GetTaskRequest/properties/params/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/GetTaskSuccessResponse/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/GetTaskSuccessResponse/properties/result/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/HTTPAuthSecurityScheme/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/InternalError/properties/code/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/InvalidAgentResponseError/properties/code/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/InvalidParamsError/properties/code/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/InvalidRequestError/properties/code/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/JSONParseError/properties/code/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/JSONRPCErrorResponse/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/JSONRPCMessage/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/JSONRPCRequest/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/JSONRPCRequest/properties/params/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/JSONRPCSuccessResponse/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/Message/properties/kind/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/Message/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Message/properties/role/enumenum_with_type

Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types

/definitions/MessageSendConfiguration/properties/pushNotificationConfig/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/MessageSendParams/properties/configuration/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/MessageSendParams/properties/message/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/MessageSendParams/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/MethodNotFoundError/properties/code/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/OAuth2SecurityScheme/properties/flows/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/OAuth2SecurityScheme/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/OAuthFlows/properties/authorizationCode/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/OAuthFlows/properties/clientCredentials/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/OAuthFlows/properties/implicit/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/OAuthFlows/properties/password/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/OpenIdConnectSecurityScheme/properties/type/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/PartBase/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/PushNotificationNotSupportedError/properties/code/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/SendMessageRequest/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/SendMessageRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/SendMessageRequest/properties/params/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/SendMessageSuccessResponse/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/SendStreamingMessageRequest/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/SendStreamingMessageRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/SendStreamingMessageRequest/properties/params/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/SendStreamingMessageSuccessResponse/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/SetTaskPushNotificationConfigRequest/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/SetTaskPushNotificationConfigRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/SetTaskPushNotificationConfigRequest/properties/params/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/SetTaskPushNotificationConfigSuccessResponse/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/SetTaskPushNotificationConfigSuccessResponse/properties/result/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/Task/properties/kind/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/Task/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/Task/properties/status/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/TaskArtifactUpdateEvent/properties/artifact/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/TaskArtifactUpdateEvent/properties/kind/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/TaskArtifactUpdateEvent/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/TaskIdParams/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/TaskNotCancelableError/properties/code/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/TaskNotFoundError/properties/code/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/TaskPushNotificationConfig/properties/pushNotificationConfig/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/TaskQueryParams/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/TaskResubscriptionRequest/properties/jsonrpc/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/TaskResubscriptionRequest/properties/method/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/TaskResubscriptionRequest/properties/params/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/TaskState/enumenum_with_type

Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types

/definitions/TaskStatus/properties/message/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/TaskStatusUpdateEvent/properties/kind/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/TaskStatusUpdateEvent/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/TaskStatusUpdateEvent/properties/status/descriptiondraft_ref_siblings

In Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated

/definitions/TextPart/properties/kind/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type

/definitions/TextPart/properties/metadata/additionalPropertiesadditional_properties_default

Setting the `additionalProperties` keyword to the true schema does not add any further constraint

/definitions/UnsupportedOperationError/properties/code/constconst_with_type

Setting `type` alongside `const` is considered an anti-pattern, as the constant already implies its respective type