Skip to main content
Glama

create-prepared-query

Define prepared queries to efficiently retrieve data from Consul MCP Server, specifying services, nearest nodes, and datacenters for targeted results.

Instructions

Create a new prepared query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datacentersNoDatacenters to query
nameNoName of the prepared query
nearestNNoNumber of nearest nodes to return
serviceNoService to query

Implementation Reference

  • The asynchronous handler function that implements the core logic of the 'create-prepared-query' tool by calling consul.query.create to create a prepared query in Consul and handling the response or errors.
    async ({ name, service, nearestN, datacenters }) => {
      try {
        // @ts-ignore - The Consul type definitions are incomplete
        const query = await consul.query.create({
          Name: name,
          Service: {
            Service: service,
            Failover: {
              NearestN: nearestN || 3,
              Datacenters: datacenters || [],
            },
          },
        }) as PreparedQuery;
        return { content: [{ type: "text", text: `Created prepared query: ${query.ID}` }] };
      } catch (error) {
        console.error("Error creating prepared query:", error);
        return { content: [{ type: "text", text: `Error creating prepared query: ${name}` }] };
      }
    }
  • Zod schema defining the input parameters for the 'create-prepared-query' tool, including name, service, nearestN, and datacenters.
    {
      name: z.string().default("").describe("Name of the prepared query"),
      service: z.string().default("").describe("Service to query"),
      nearestN: z.number().optional().describe("Number of nearest nodes to return"),
      datacenters: z.array(z.string()).optional().describe("Datacenters to query"),
    },
  • The server.tool call that registers the 'create-prepared-query' tool with its description, input schema, and handler function.
    server.tool(
      "create-prepared-query",
      "Create a new prepared query",
      {
        name: z.string().default("").describe("Name of the prepared query"),
        service: z.string().default("").describe("Service to query"),
        nearestN: z.number().optional().describe("Number of nearest nodes to return"),
        datacenters: z.array(z.string()).optional().describe("Datacenters to query"),
      },
      async ({ name, service, nearestN, datacenters }) => {
        try {
          // @ts-ignore - The Consul type definitions are incomplete
          const query = await consul.query.create({
            Name: name,
            Service: {
              Service: service,
              Failover: {
                NearestN: nearestN || 3,
                Datacenters: datacenters || [],
              },
            },
          }) as PreparedQuery;
          return { content: [{ type: "text", text: `Created prepared query: ${query.ID}` }] };
        } catch (error) {
          console.error("Error creating prepared query:", error);
          return { content: [{ type: "text", text: `Error creating prepared query: ${name}` }] };
        }
      }
    );
  • TypeScript interface defining the structure of a PreparedQuery response from Consul, used in the tool's handler.
    interface PreparedQuery {
      ID: string;
      Name: string;
      Service: {
        Service: string;
        Failover: {
          NearestN: number;
          Datacenters: string[];
        };
      };
    }
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. It states 'Create' which implies a write/mutation operation, but it doesn't disclose behavioral traits such as required permissions, idempotency, side effects, or what happens on failure. This is inadequate for a mutation tool with zero annotation coverage.

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 and front-loaded, making it easy to parse 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 complexity of a mutation tool with 4 parameters and no annotations or output schema, the description is incomplete. It lacks context on what a prepared query is, how it's used, what the creation entails, and what the expected outcome or return values are, making it insufficient for effective tool selection.

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 description adds no parameter semantics beyond what the input schema provides. With 100% schema description coverage, the schema already documents all 4 parameters (datacenters, name, nearestN, service). The description doesn't explain how these parameters interact or their purpose in creating a prepared query, so it meets the baseline but adds no extra value.

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

Purpose3/5

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

The description 'Create a new prepared query' clearly states the action (create) and resource (prepared query), but it's vague about what a 'prepared query' entails in this context. It doesn't distinguish this tool from other creation tools like 'register-service' or 'put-kv', which limits its specificity.

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. With sibling tools like 'execute-prepared-query' and 'list-sessions', there's no indication of prerequisites, dependencies, or scenarios where this tool is appropriate, leaving usage unclear.

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