Skip to main content
Glama

get_gcp_usage_settings

Read-onlyIdempotent

The BigQuery job usage settings saved on the GCP connection: bigquery_job_usage and scheduled_query_owners ("on"), and bigquery_job_regions. A setting that is not saved is absent (off, or regions discovered). Never returns credentials. Change them with set_gcp_usage_settings. Mirrors GET /api/accounts/:accountId/connections/gcp/usage-settings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_gcp_usage_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that: it explains the absent-means-off-or-auto-discovered semantics, guarantees credentials are never returned, and pins behavior to the documented API endpoint. Return format details are implied by the field enumeration rather than spelled out.

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

Conciseness4/5

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

Three tight sentences, front-loaded with what is returned and followed by the absence semantics and the setter pointer. The final sentence mirroring the REST endpoint is mildly redundant but serves as a grounding anchor; nothing else is wasted.

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?

There is no output schema, so the description carries the burden of describing the return value, and it does so by naming the settings keys and explaining how absence encodes state. Combined with the credentials caveat and the setter pointer, an agent has everything needed to call and interpret this tool.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description's field discussion describes output rather than input, which is appropriate here.

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?

States a specific verb and resource (get the BigQuery job usage settings on the GCP connection) and enumerates the concrete fields returned: bigquery_job_usage, scheduled_query_owners, and bigquery_job_regions. That level of specificity separates it from the many list_* and get_* siblings without requiring the agent to open a schema.

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

Usage Guidelines4/5

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

Explicitly routes mutation intent elsewhere by naming set_gcp_usage_settings as the way to change these values, which is exactly the when-not-to-use signal an agent needs. It does not cover when to prefer this over other GCP or usage-related tools, but for a zero-argument getter the alternative that matters is the setter and it is named.

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.

Resources