Skip to main content
Glama

list_usage_dimensions

Read-onlyIdempotent

List the distinct values seen for a usage dimension ("metric" or "external_customer_id") over a date range — useful for discovering filter values before calling query_usage. Each entry pairs the raw value with a label (for external_customer_id, the customer's name from account_customers when known, falling back to the id itself). Use "dimension_key" to list the keys of the pushed dimensions map; BigQuery job usage uses user_email (the user who ran the job), region, project_id, dts_config_id and query_hash. Mirrors GET /api/usage/dimensions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dimension": "<dimension>"
    },
    "name": "list_usage_dimensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNo
dimensionYes"metric", "external_customer_id", "dimension_key" (the keys of the pushed dimensions map) or "dimension:<key>" (that key's values)
start_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / dimension / description
      Added value: +"\"metric\", \"external_customer_id\", \"dimension_key\" (the keys of the pushed dimensions map) or \"dimension:<key>\" (that key's values)"
    • removedInput schema / properties / dimension / enum
      Removed value: -[
      -  "metric",
      -  "external_customer_id"
      -]
    • addedInput schema / properties / dimension / pattern
      Added value: +"^(metric|external_customer_id|dimension_key|dimension:[A-Za-z0-9_.-]{1,64})$"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds real behavioral value on top: the shape of each entry (`value` plus a human-readable `label`, with the fallback rule for external_customer_id), and the REST endpoint it mirrors. It does not cover ordering, pagination, or behavior when the range yields nothing.

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?

Front-loaded with purpose and the query_usage relationship, then the return shape, then the dimension_key caveat. Every sentence carries information, though the BigQuery key enumeration is the one item that could be moved to a reference and trimmed.

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

Completeness3/5

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

With no output schema, the description carries the burden of explaining returns and does so at a high level (value/label pairs). However, for a tool with two undocumented date parameters and no stated date format, ordering, or empty-result behavior, the definition is adequate but leaves gaps an agent may hit on first call.

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 33%, and the description only expands on `dimension` – clarifying metric vs external_customer_id, the dimension_key variant, and listing valid BigQuery keys for dimension:<key>. The `start_date` and `end_date` parameters are left undocumented in both the schema and the description, including their expected string format.

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 ("List the distinct values seen for a usage dimension") and pins the scope to a date range. It immediately distinguishes itself from query_usage by describing this as a discovery step rather than an aggregation call.

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 names the context of use: "useful for discovering filter values before calling query_usage." It also clarifies the dimension_key variant for pushed dimensions and enumerates the BigQuery job keys, which tells the agent which value to pick. It stops short of any when-not guidance, so a 4 rather than 5.

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