Skip to main content
Glama

execute_sql_readonly

Read-onlyIdempotent

Run a read-only SQL query in the project and return the result. Prefer this tool over execute_sql if possible.

This tool is restricted to only SELECT statements. INSERT, UPDATE, and DELETE statements and stored procedures aren't allowed. If the query doesn't include a SELECT statement, an error is returned. For information on creating queries, see the GoogleSQL documentation.

Example Queries:

-- Count the number of penguins in each island.
SELECT island, COUNT(*) AS population
FROM bigquery-public-data.ml_datasets.penguins GROUP BY island

-- Evaluate a bigquery ML Model.
SELECT * FROM ML.EVALUATE(MODEL `my_dataset.my_model`)

-- Evaluate BigQuery ML model on custom data
SELECT *
FROM ML.EVALUATE(MODEL `my_dataset.my_model`, (SELECT * FROM `my_dataset.my_table`))

-- Predict using BigQuery ML model:
SELECT *
FROM ML.PREDICT(MODEL `my_dataset.my_model`, (SELECT * FROM `my_dataset.my_table`))

-- Forecast data using AI.FORECAST
SELECT *
FROM AI.FORECAST(TABLE `project.dataset.my_table`, data_col => 'num_trips',
  timestamp_col => 'date', id_cols => ['usertype'], horizon => 30)

Queries executed using the execute_sql_readonly tool will always have the job label goog-mcp-server: true automatically set in addition to any custom labels provided in the request. Queries are charged to the project specified in the project_id field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesRequired. The query to execute in the form of a GoogleSQL query.
dryRunNoOptional. If set to true, BigQuery doesn't run the job. Instead, if the query is valid, BigQuery returns statistics about the job such as how many bytes would be processed. If the query is invalid, an error returns. The default value is false.
labelsNoOptional. The labels associated with this query. Labels can be used to organize and group query jobs. Label keys and values can be no longer than 63 characters, can only contain lowercase letters, numeric characters, underscores and dashes. International characters are allowed. Label keys must start with a letter and each label in the map must have a different key.
projectIdYesRequired. Project that will be used for query execution and billing.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsNoAn object with as many results as can be contained within the maximum permitted reply size. To get any additional rows, you can call GetQueryResults and specify the jobReference returned above.
errorsNoOutput only. The first errors or warnings encountered during the running of the job. The final message includes the number of errors that caused the process to stop. Errors here do not necessarily mean that the job has completed or was unsuccessful. For more information about error messages, see [Error messages](https://cloud.google.com/bigquery/docs/error-messages).
schemaNoThe schema of the results. Present only when the query completes successfully.
queryIdNoOutput only. The ID of the query.
jobCompleteNoWhether the query has completed or not. If rows or totalRows are present, this will always be true. If this is false, totalRows will not be available.
totalSlotMsNoOutput only. Number of slot ms the user is actually billed for.
totalBytesBilledNoOutput only. The total number of bytes billed for the query. Only applies if the project is configured to use on-demand pricing.
numDmlAffectedRowsNoOutput only. The number of rows affected by a DML statement.
totalBytesProcessedNoOutput only. The total number of bytes processed for this query.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / labels
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "description": "Optional. The labels associated with this query. Labels can be used to organize and group query jobs. Label keys and values can be no longer than 63 characters, can only contain lowercase letters, numeric characters, underscores and dashes. International characters are allowed. Label keys must start with a letter and each label in the map must have a different key.",
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."
  3. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
  4. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."
  5. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
  6. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."
  7. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
  8. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."
  9. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
  10. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."
  11. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
  12. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."
  13. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
  14. Changed2 schema fields changed
    • changedOutput schema / $defs / DataGovernanceTagsInfo / properties / dataGovernanceTags / description
      Previous value: -"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""New value: +"Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"parent-id/pii\" where parent-id is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"parent-id/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\""
    • changedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo / description
      Previous value: -"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."New value: +"Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: * **Precedence**: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. * **Patching behavior**: Describes how this field behaves during a `Table.patch` schema update: * **Unset**: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. * **Empty Field**: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This removes all tags from the column. * **Updating tags**: To replace an existing tag, send the field with the new tag."
  15. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."
  16. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."
  17. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."
  18. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."
  19. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."
  20. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."
  21. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."
  22. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."
  23. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."
  24. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."
  25. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."
  26. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."
  27. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."
  28. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."
  29. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."
  30. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."
  31. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."
  32. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."
  33. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."
  34. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."
  35. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."
  36. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."
  37. Changed1 schema field changed
    • changedOutput schema / $defs / GeneratedExpressionInfo / properties / generationExpression / description
      Previous value: -"Optional. The generation expression (e.g. AI.EMBED(...)) used to generated the field."New value: +"Optional. The generation expression (e.g. AI.EMBED(...)) used to generate the field."
  38. Changed4 schema fields changed
    • addedOutput schema / $defs / DataGovernanceTagsInfo
      Added value: +{
      +  "properties": {
      +    "dataGovernanceTags": {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "description": "Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\"",
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / $defs / DataPolicyList
      Added value: +{
      +  "description": "A list of data policy options. For more information, see [Mask data by applying data policies to a column](https://docs.cloud.google.com/bigquery/docs/column-data-masking#data-policies-on-column).",
      +  "properties": {
      +    "dataPolicies": {
      +      "description": "Contains a list of data policy options. At most 9 data policies are allowed per field.",
      +      "items": {
      +        "$ref": "#/$defs/DataPolicyOption"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo
      Added value: +{
      +  "$ref": "#/$defs/DataGovernanceTagsInfo",
      +  "description": "Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
      +}
    • addedOutput schema / $defs / TableFieldSchema / properties / dataPolicyList
      Added value: +{
      +  "$ref": "#/$defs/DataPolicyList",
      +  "description": "Optional. Specifies data policies attached to this field, used for field-level access control. When set, this will be the source of truth for data policy information."
      +}
  39. Changed4 schema fields changed
    • removedOutput schema / $defs / DataGovernanceTagsInfo
      Removed value: -{
      -  "properties": {
      -    "dataGovernanceTags": {
      -      "additionalProperties": {
      -        "type": "string"
      -      },
      -      "description": "Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\"",
      -      "type": "object"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / $defs / DataPolicyList
      Removed value: -{
      -  "description": "A list of data policy options. For more information, see [Mask data by applying data policies to a column](https://docs.cloud.google.com/bigquery/docs/column-data-masking#data-policies-on-column).",
      -  "properties": {
      -    "dataPolicies": {
      -      "description": "Contains a list of data policy options. At most 9 data policies are allowed per field.",
      -      "items": {
      -        "$ref": "#/$defs/DataPolicyOption"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo
      Removed value: -{
      -  "$ref": "#/$defs/DataGovernanceTagsInfo",
      -  "description": "Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
      -}
    • removedOutput schema / $defs / TableFieldSchema / properties / dataPolicyList
      Removed value: -{
      -  "$ref": "#/$defs/DataPolicyList",
      -  "description": "Optional. Specifies data policies attached to this field, used for field-level access control. When set, this will be the source of truth for data policy information."
      -}
  40. Changed4 schema fields changed
    • addedOutput schema / $defs / DataGovernanceTagsInfo
      Added value: +{
      +  "properties": {
      +    "dataGovernanceTags": {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "description": "Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\"",
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / $defs / DataPolicyList
      Added value: +{
      +  "description": "A list of data policy options. For more information, see [Mask data by applying data policies to a column](https://docs.cloud.google.com/bigquery/docs/column-data-masking#data-policies-on-column).",
      +  "properties": {
      +    "dataPolicies": {
      +      "description": "Contains a list of data policy options. At most 9 data policies are allowed per field.",
      +      "items": {
      +        "$ref": "#/$defs/DataPolicyOption"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo
      Added value: +{
      +  "$ref": "#/$defs/DataGovernanceTagsInfo",
      +  "description": "Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
      +}
    • addedOutput schema / $defs / TableFieldSchema / properties / dataPolicyList
      Added value: +{
      +  "$ref": "#/$defs/DataPolicyList",
      +  "description": "Optional. Specifies data policies attached to this field, used for field-level access control. When set, this will be the source of truth for data policy information."
      +}
  41. Changed4 schema fields changed
    • removedOutput schema / $defs / DataGovernanceTagsInfo
      Removed value: -{
      -  "properties": {
      -    "dataGovernanceTags": {
      -      "additionalProperties": {
      -        "type": "string"
      -      },
      -      "description": "Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\"",
      -      "type": "object"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / $defs / DataPolicyList
      Removed value: -{
      -  "description": "A list of data policy options. For more information, see [Mask data by applying data policies to a column](https://docs.cloud.google.com/bigquery/docs/column-data-masking#data-policies-on-column).",
      -  "properties": {
      -    "dataPolicies": {
      -      "description": "Contains a list of data policy options. At most 9 data policies are allowed per field.",
      -      "items": {
      -        "$ref": "#/$defs/DataPolicyOption"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo
      Removed value: -{
      -  "$ref": "#/$defs/DataGovernanceTagsInfo",
      -  "description": "Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
      -}
    • removedOutput schema / $defs / TableFieldSchema / properties / dataPolicyList
      Removed value: -{
      -  "$ref": "#/$defs/DataPolicyList",
      -  "description": "Optional. Specifies data policies attached to this field, used for field-level access control. When set, this will be the source of truth for data policy information."
      -}
  42. Changed4 schema fields changed
    • addedOutput schema / $defs / DataGovernanceTagsInfo
      Added value: +{
      +  "properties": {
      +    "dataGovernanceTags": {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "description": "Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\"",
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / $defs / DataPolicyList
      Added value: +{
      +  "description": "A list of data policy options. For more information, see [Mask data by applying data policies to a column](https://docs.cloud.google.com/bigquery/docs/column-data-masking#data-policies-on-column).",
      +  "properties": {
      +    "dataPolicies": {
      +      "description": "Contains a list of data policy options. At most 9 data policies are allowed per field.",
      +      "items": {
      +        "$ref": "#/$defs/DataPolicyOption"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo
      Added value: +{
      +  "$ref": "#/$defs/DataGovernanceTagsInfo",
      +  "description": "Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
      +}
    • addedOutput schema / $defs / TableFieldSchema / properties / dataPolicyList
      Added value: +{
      +  "$ref": "#/$defs/DataPolicyList",
      +  "description": "Optional. Specifies data policies attached to this field, used for field-level access control. When set, this will be the source of truth for data policy information."
      +}
  43. Changed4 schema fields changed
    • removedOutput schema / $defs / DataGovernanceTagsInfo
      Removed value: -{
      -  "properties": {
      -    "dataGovernanceTags": {
      -      "additionalProperties": {
      -        "type": "string"
      -      },
      -      "description": "Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\"",
      -      "type": "object"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / $defs / DataPolicyList
      Removed value: -{
      -  "description": "A list of data policy options. For more information, see [Mask data by applying data policies to a column](https://docs.cloud.google.com/bigquery/docs/column-data-masking#data-policies-on-column).",
      -  "properties": {
      -    "dataPolicies": {
      -      "description": "Contains a list of data policy options. At most 9 data policies are allowed per field.",
      -      "items": {
      -        "$ref": "#/$defs/DataPolicyOption"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo
      Removed value: -{
      -  "$ref": "#/$defs/DataGovernanceTagsInfo",
      -  "description": "Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
      -}
    • removedOutput schema / $defs / TableFieldSchema / properties / dataPolicyList
      Removed value: -{
      -  "$ref": "#/$defs/DataPolicyList",
      -  "description": "Optional. Specifies data policies attached to this field, used for field-level access control. When set, this will be the source of truth for data policy information."
      -}
  44. Changed4 schema fields changed
    • addedOutput schema / $defs / DataGovernanceTagsInfo
      Added value: +{
      +  "properties": {
      +    "dataGovernanceTags": {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "description": "Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\"",
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / $defs / DataPolicyList
      Added value: +{
      +  "description": "A list of data policy options. For more information, see [Mask data by applying data policies to a column](https://docs.cloud.google.com/bigquery/docs/column-data-masking#data-policies-on-column).",
      +  "properties": {
      +    "dataPolicies": {
      +      "description": "Contains a list of data policy options. At most 9 data policies are allowed per field.",
      +      "items": {
      +        "$ref": "#/$defs/DataPolicyOption"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo
      Added value: +{
      +  "$ref": "#/$defs/DataGovernanceTagsInfo",
      +  "description": "Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
      +}
    • addedOutput schema / $defs / TableFieldSchema / properties / dataPolicyList
      Added value: +{
      +  "$ref": "#/$defs/DataPolicyList",
      +  "description": "Optional. Specifies data policies attached to this field, used for field-level access control. When set, this will be the source of truth for data policy information."
      +}
  45. Changed4 schema fields changed
    • removedOutput schema / $defs / DataGovernanceTagsInfo
      Removed value: -{
      -  "properties": {
      -    "dataGovernanceTags": {
      -      "additionalProperties": {
      -        "type": "string"
      -      },
      -      "description": "Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\"",
      -      "type": "object"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / $defs / DataPolicyList
      Removed value: -{
      -  "description": "A list of data policy options. For more information, see [Mask data by applying data policies to a column](https://docs.cloud.google.com/bigquery/docs/column-data-masking#data-policies-on-column).",
      -  "properties": {
      -    "dataPolicies": {
      -      "description": "Contains a list of data policy options. At most 9 data policies are allowed per field.",
      -      "items": {
      -        "$ref": "#/$defs/DataPolicyOption"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo
      Removed value: -{
      -  "$ref": "#/$defs/DataGovernanceTagsInfo",
      -  "description": "Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
      -}
    • removedOutput schema / $defs / TableFieldSchema / properties / dataPolicyList
      Removed value: -{
      -  "$ref": "#/$defs/DataPolicyList",
      -  "description": "Optional. Specifies data policies attached to this field, used for field-level access control. When set, this will be the source of truth for data policy information."
      -}
  46. Changed4 schema fields changed
    • addedOutput schema / $defs / DataGovernanceTagsInfo
      Added value: +{
      +  "properties": {
      +    "dataGovernanceTags": {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "description": "Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\"",
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / $defs / DataPolicyList
      Added value: +{
      +  "description": "A list of data policy options. For more information, see [Mask data by applying data policies to a column](https://docs.cloud.google.com/bigquery/docs/column-data-masking#data-policies-on-column).",
      +  "properties": {
      +    "dataPolicies": {
      +      "description": "Contains a list of data policy options. At most 9 data policies are allowed per field.",
      +      "items": {
      +        "$ref": "#/$defs/DataPolicyOption"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo
      Added value: +{
      +  "$ref": "#/$defs/DataGovernanceTagsInfo",
      +  "description": "Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
      +}
    • addedOutput schema / $defs / TableFieldSchema / properties / dataPolicyList
      Added value: +{
      +  "$ref": "#/$defs/DataPolicyList",
      +  "description": "Optional. Specifies data policies attached to this field, used for field-level access control. When set, this will be the source of truth for data policy information."
      +}
  47. Changed4 schema fields changed
    • removedOutput schema / $defs / DataGovernanceTagsInfo
      Removed value: -{
      -  "properties": {
      -    "dataGovernanceTags": {
      -      "additionalProperties": {
      -        "type": "string"
      -      },
      -      "description": "Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\"",
      -      "type": "object"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / $defs / DataPolicyList
      Removed value: -{
      -  "description": "A list of data policy options. For more information, see [Mask data by applying data policies to a column](https://docs.cloud.google.com/bigquery/docs/column-data-masking#data-policies-on-column).",
      -  "properties": {
      -    "dataPolicies": {
      -      "description": "Contains a list of data policy options. At most 9 data policies are allowed per field.",
      -      "items": {
      -        "$ref": "#/$defs/DataPolicyOption"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo
      Removed value: -{
      -  "$ref": "#/$defs/DataGovernanceTagsInfo",
      -  "description": "Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
      -}
    • removedOutput schema / $defs / TableFieldSchema / properties / dataPolicyList
      Removed value: -{
      -  "$ref": "#/$defs/DataPolicyList",
      -  "description": "Optional. Specifies data policies attached to this field, used for field-level access control. When set, this will be the source of truth for data policy information."
      -}
  48. Changed4 schema fields changed
    • addedOutput schema / $defs / DataGovernanceTagsInfo
      Added value: +{
      +  "properties": {
      +    "dataGovernanceTags": {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "description": "Optional. The data governance tags added to this field are used for field-level access control. Only one data governance tag is currently supported on a field. Tag keys are globally unique. Tag key is expected to be in the namespaced format, for example \"123456789012/pii\" where 123456789012 is the ID of the parent organization or project resource for this tag key. Tag value is expected to be the short name, for example \"sensitive\". See [Tag definitions](https://cloud.google.com/iam/docs/tags-access-control#definitions) for more details. For example: \"123456789012/pii\": \"sensitive\", \"myProject/cost_center\": \"sales\"",
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / $defs / DataPolicyList
      Added value: +{
      +  "description": "A list of data policy options. For more information, see [Mask data by applying data policies to a column](https://docs.cloud.google.com/bigquery/docs/column-data-masking#data-policies-on-column).",
      +  "properties": {
      +    "dataPolicies": {
      +      "description": "Contains a list of data policy options. At most 9 data policies are allowed per field.",
      +      "items": {
      +        "$ref": "#/$defs/DataPolicyOption"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / $defs / TableFieldSchema / properties / dataGovernanceTagsInfo
      Added value: +{
      +  "$ref": "#/$defs/DataGovernanceTagsInfo",
      +  "description": "Optional. Specifies the data governance tags on this field. This field works with other column-level security fields as follows: - Precedence: If a data governance tag is attached to a column, it takes precedence over the policy tag attached to the column. However, if a data policy is attached to a column, it takes precedence over the data governance tag. - Patching behavior (how this field behaves during a `Table.patch` schema update): - Unset: If the `data_governance_tags_info` field is omitted from the update request, the existing tags on the column are preserved. - Empty Field: To clear data governance tags from a column, send the `data_governance_tags_info` field as an empty object. This will remove all tags from the column. - Updating tags: To replace existing tag, send the field with the new tag."
      +}
    • addedOutput schema / $defs / TableFieldSchema / properties / dataPolicyList
      Added value: +{
      +  "$ref": "#/$defs/DataPolicyList",
      +  "description": "Optional. Specifies data policies attached to this field, used for field-level access control. When set, this will be the source of truth for data policy information."
      +}
  49. Added
  50. Removed
  51. Added
  52. Removed
  53. Added
  54. Removed
  55. Added
  56. Removed
  57. Added
  58. Removed
  59. Added
  60. Removed
  61. Added
  62. Removed
  63. Added

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint and idempotentHint annotations, the description discloses key behaviors: only SELECT queries are accepted, non-SELECT queries return an error, a job label is automatically set, and queries are billed to the specified project. This gives the agent useful operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but well-structured and purposeful. The purpose and restriction are front-loaded, followed by relevant examples and operational notes. The example queries earn their place because they demonstrate valid SELECT, ML.EVALUATE, ML.PREDICT, and AI.FORECAST usage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete for this tool: it states what the tool does, when to prefer it, what restrictions apply, what error behavior to expect, and provides concrete query examples. The output schema covers return-value expectations, so no additional return-format detail is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameter definitions already carry the semantic load. The description adds helpful examples and notes about billing, but it does not significantly expand on the parameter meanings beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Run a read-only SQL query in the project and return the result.' It also explicitly distinguishes itself from execute_sql by restricting to SELECT statements, so an agent can clearly identify its purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit routing instruction: 'Prefer this tool over execute_sql if possible.' It also defines when not to use it by stating that INSERT, UPDATE, DELETE, and stored procedures are not allowed and will produce an error, making the alternative usage clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

The two SQL execution tools overlap in that both return query results, but the read-only variant is clearly scoped to SELECT statements and both descriptions direct agents to prefer it when possible. The four metadata tools cleanly separate dataset vs table and listing vs info, so misselection risk is low but not nonexistent.

Naming Consistency5/5

All tools follow a consistent lowercase snake_case verb_noun pattern: execute_sql, execute_sql_readonly, get_*_info, list_*_ids. The read-only suffix and consistent get/list prefixes make the tool set predictable and easy to navigate.

Tool Count5/5

Six tools is an appropriate size for a BigQuery MCP server: two query execution variants plus four metadata discovery tools. Each tool has a clear role, and the count is neither thin nor bloated.

Completeness4/5

The query tools cover read and write operations, including DDL/DML and ML functions, while the metadata tools cover dataset and table discovery. There are no direct tools for job management, loading data, or model management, but execute_sql can handle most lifecycle operations, so the gaps are workable.

Resources