Skip to main content
Glama

logs_label_values

Retrieve all values for a specified Loki label, such as app names or namespaces, to identify available log filters and query targets.

Instructions

Get all values for a Loki label (e.g. all app names, namespaces, components).

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": {
      "label": "<label>"
    },
    "name": "logs_label_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYesLabel name (e.g. "app", "namespace", "component")
targetNoNamed backend instance to query (configured: default). Defaults to the primary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It implies a read-only enumeration scoped to a named backend via the 'target' parameter, but omits cardinality risk (labels such as pod can return thousands of values), whether results require a time range, and whether values are deduplicated or sorted. Useful but thin for a zero-annotation tool.

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?

One front-loaded sentence with zero filler that states the action and gives concrete examples. It is efficient, though quite short for a discovery tool, leaving notable behavioral questions unanswered.

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

Completeness2/5

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

For a read-only enumeration tool with no annotations and no output schema, the description says nothing about the return shape (string list vs objects), result volume, or whether values are constrained by time range or backend. An agent must guess how to interpret the response. This is a meaningful gap given the absence of structured behavioral metadata.

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%, and both parameters ('label' and 'target' with the configured default) are documented in the schema. The description's examples duplicate the schema's own example rather than adding new meaning, so the baseline of 3 is appropriate.

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 all values for a Loki label', with parenthetical examples ('all app names, namespaces, components') clarifying that the result is the value set rather than label names. That distinguishes it from the logs_labels sibling (list labels).

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

Usage Guidelines3/5

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

Usage is implied — enumerate a label's values, e.g. to construct a filter for logs_query — but the description never states when to prefer it over logs_labels and logs_labels, or which labels are actually valid choices. No explicit conditions or alternatives are given.

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