Skip to main content
Glama

destroy-session

Terminate a Consul session by its ID to release associated locks and resources. This tool is essential for managing distributed system states and ensuring cleanup.

Instructions

Destroy a session in Consul

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoID of the session to destroy

Implementation Reference

  • Registration of the 'destroy-session' tool, including inline schema for the session ID parameter and the handler function that destroys the Consul session using consul.session.destroy(id).
    server.tool(
      "destroy-session",
      "Destroy a session in Consul",
      {
        id: z.string().default("").describe("ID of the session to destroy"),
      },
      async ({ id }) => {
        try {
          const success = await consul.session.destroy(id);
          if (!success) {
            return { content: [{ type: "text", text: `Failed to destroy session with ID: ${id}` }] };
          }
    
          return { content: [{ type: "text", text: `Successfully destroyed session with ID: ${id}` }] };
        } catch (error) {
          console.error("Error destroying session:", error);
          return { content: [{ type: "text", text: `Error destroying session with ID: ${id}` }] };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the destructive action but doesn't explain what 'destroy' entails (permanent deletion, revocation, side effects), authentication requirements, error conditions, or rate limits. This is inadequate for a mutation tool.

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 wasted words. It's appropriately sized for a simple tool and front-loads the essential information.

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 destructive mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after destruction, error handling, or provide context about sessions in Consul. Given the complexity and lack of structured data, more completeness is needed.

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%, with the single parameter 'id' documented as 'ID of the session to destroy'. The description doesn't add any meaningful semantics beyond what the schema already provides, so it meets the baseline for high schema coverage.

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 ('Destroy') and resource ('a session in Consul'), providing specific verb+resource. However, it doesn't differentiate from sibling tools like 'list-sessions' or explain what a 'session' is in Consul context, preventing a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing session ID), consequences of destruction, or when to choose this over other session-related operations.

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