Skip to main content
Glama
yincongcyincong

VictoriaMetrics-mcp-server

vm_label_values

Retrieve all unique values for a specific label in VictoriaMetrics to filter and analyze time series data effectively.

Instructions

Get all unique values for a specific label

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesLabel name to retrieve values for

Implementation Reference

  • The handler function `vmLabelValues` that executes the tool logic: fetches unique values for the given label from VictoriaMetrics API endpoint `/api/v1/label/{label}/values` and returns the data as JSON or error.
    async function vmLabelValues(label) {
      let urlStr = VM_URL
      if (urlStr === "") {
        urlStr = VM_SELECT_URL
      }
      const url = new URL(urlStr + "/api/v1/label/"+ label +"/values");
      const response = await fetch(url.toString());
      const data = await response.json();
    
      if (data.status === "success") {
        return {
          content: [{
            type: "text",
            text: JSON.stringify(data.data),
          }],
          isError: false
        };
      } else {
        return {
          content: [{
            type: "text",
            text: "range query fail:" + await response.text(),
          }],
          isError: true
        };
      }
    }
  • The tool schema definition for `vm_label_values`, including input schema requiring a `label` string parameter.
    const VM_LABEL_VALUES_TOOL = {
      name: "vm_label_values",
      description: "Get all unique values for a specific label",
      inputSchema: {
        type: "object",
        properties: {
          label: {
            type: "string",
            description: "Label name to retrieve values for",
          }
        },
        required: ["label"],
      }
    };
  • src/index.js:127-134 (registration)
    Registration of the tool in the `VM_TOOLS` array, which is returned by the ListToolsRequestSchema handler for tool discovery.
    const VM_TOOLS = [
      VM_DATA_WRITE_TOOL,
      VM_QUERY_RANGE_TOOL,
      VM_QUERY_TOOL,
      VM_LABELS_TOOL,
      VM_LABEL_VALUES_TOOL,
      VM_PROMETHEUS_WRITE_TOOL
    ];
  • src/index.js:359-362 (registration)
    The switch case in the CallToolRequestSchema handler that dispatches to the `vmLabelValues` handler function.
    case "vm_label_values": {
      const {label} = request.params.arguments;
      return await vmLabelValues(label);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a read operation ('Get'), but does not cover aspects like rate limits, authentication requirements, error handling, or the format of returned values. This leaves significant gaps in understanding the tool's behavior.

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 a single, clear sentence with no wasted words, making it highly concise and front-loaded. It efficiently conveys the core purpose without unnecessary elaboration.

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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what the tool returns (e.g., list format, data types) or address behavioral aspects like performance or errors, which are crucial for a tool with no structured output information.

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?

The input schema has 100% description coverage, with the 'label' parameter documented as 'Label name to retrieve values for'. The description adds no additional meaning beyond this, such as examples or constraints, so it meets the baseline for high schema coverage without compensating further.

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

Purpose4/5

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

The description clearly states the verb 'Get' and the resource 'all unique values for a specific label', making the purpose evident. However, it does not explicitly differentiate from sibling tools like 'vm_labels' (which might list labels rather than values), leaving some ambiguity in sibling context.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as 'vm_labels' or 'vm_query', nor does it mention prerequisites or exclusions. It lacks explicit usage context, relying solely on the implied need to retrieve label values.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yincongcyincong/VictoriaMetrics-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server