Skip to main content
Glama

list-kv

Filter and list keys in the Consul KV store using a specified prefix to organize and retrieve stored data efficiently.

Instructions

List keys in the KV store

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prefixNoPrefix to filter keys by

Implementation Reference

  • The handler function that implements the logic for listing keys in the Consul KV store. It calls consul.kv.keys(prefix), handles empty results and errors, and formats the output as text.
    async ({ prefix = "" }) => {
      try {
        const data = await consul.kv.keys(prefix);
        if (!data || data.length === 0) {
          return { content: [{ type: "text", text: `No keys found${prefix ? ` with prefix: ${prefix}` : ""}` }] };
        }
        
        const keysText = `Keys in KV store${prefix ? ` with prefix: ${prefix}` : ""}:\n\n${data.join("\n")}`;
        return { content: [{ type: "text", text: keysText }] };
      } catch (error) {
        console.error("Error listing KV keys:", error);
        return { content: [{ type: "text", text: `Error listing keys${prefix ? ` with prefix: ${prefix}` : ""}` }] };
      }
    }
  • Zod schema defining the input parameter 'prefix' as an optional string.
    {
      prefix: z.string().default("").optional().describe("Prefix to filter keys by"),
    },
  • The server.tool() call that registers the 'list-kv' tool, including its name, description, input schema, and handler function.
    server.tool(
      "list-kv",
      "List keys in the KV store",
      {
        prefix: z.string().default("").optional().describe("Prefix to filter keys by"),
      },
      async ({ prefix = "" }) => {
        try {
          const data = await consul.kv.keys(prefix);
          if (!data || data.length === 0) {
            return { content: [{ type: "text", text: `No keys found${prefix ? ` with prefix: ${prefix}` : ""}` }] };
          }
          
          const keysText = `Keys in KV store${prefix ? ` with prefix: ${prefix}` : ""}:\n\n${data.join("\n")}`;
          return { content: [{ type: "text", text: keysText }] };
        } catch (error) {
          console.error("Error listing KV keys:", error);
          return { content: [{ type: "text", text: `Error listing keys${prefix ? ` with prefix: ${prefix}` : ""}` }] };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists keys but doesn't describe behavioral traits such as pagination, rate limits, authentication requirements, or what happens if no keys match the prefix. This leaves significant gaps for a tool that interacts with a data store.

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, efficient sentence with zero waste. It's appropriately sized for a simple tool and front-loaded with the core purpose, making it easy to understand quickly 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 for a tool that lists keys in a data store. It doesn't cover return values (e.g., format of the list, error handling) or important behavioral aspects like permissions or limitations, which are critical for effective use in a Consul-like context with sibling tools.

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 single parameter 'prefix' documented as 'Prefix to filter keys by'. The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema does the heavy lifting without compensating for any gaps.

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 action ('List') and resource ('keys in the KV store'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'get-kv' or 'put-kv' beyond the basic action, missing explicit differentiation about scope or granularity.

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. It doesn't mention when to choose 'list-kv' over 'get-kv' (which likely retrieves specific key values) or other sibling tools, nor does it specify any prerequisites or exclusions for usage.

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

Related 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/kocierik/consul-mcp-server'

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