Skip to main content
Glama

get_auth_status

Check QIT CLI authentication status to verify access for testing WordPress/WooCommerce plugins.

Instructions

Check if QIT CLI is authenticated and show current authentication status.

⚠️ QIT CLI not detected. QIT CLI not found. Please install it using one of these methods:

  1. Via Composer (recommended): composer require woocommerce/qit-cli --dev

  2. Set QIT_CLI_PATH environment variable: export QIT_CLI_PATH=/path/to/qit

  3. Ensure 'qit' is available in your system PATH

For more information, visit: https://github.com/woocommerce/qit-cli

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the logic for the 'get_auth_status' tool. It attempts to list extensions using the QIT CLI to verify authentication status, counts available extensions if successful, checks for specific error messages indicating authentication issues, and returns a formatted response.
    handler: async () => {
      // Try to list extensions - if it works, we're authenticated
      const result = await executeQitCommand(["extensions", "--no-interaction"]);
    
      if (result.success) {
        // Count lines that look like extension rows (start with |)
        const lines = result.stdout.split("\n");
        const extensionLines = lines.filter(line =>
          line.startsWith("|") && !line.includes("ID") && !line.includes("---")
        );
        const count = extensionLines.length;
        return {
          content: `Authenticated. You have access to ${count} extension(s). Use 'list_extensions' tool to see the full list.`,
          isError: false,
        };
      }
    
      // Check if error indicates auth issue
      const output = result.stderr || result.stdout;
      if (
        output.includes("not connected") ||
        output.includes("authenticate") ||
        output.includes("connect")
      ) {
        return {
          content:
            "Not authenticated. Use the 'authenticate' tool to connect with your WooCommerce.com Partner Developer account.",
          isError: false,
        };
      }
    
      return {
        content: `Unable to determine authentication status: ${output}`,
        isError: true,
      };
    },
  • The tool definition including name, description, and empty input schema (no parameters required).
    get_auth_status: {
      name: "get_auth_status",
      description:
        "Check if QIT CLI is authenticated and show current authentication status.",
      inputSchema: z.object({}),
  • Imports the authTools object (containing get_auth_status) and spreads it into the central allTools export, aggregating all tools in the codebase.
    import { authTools } from "./auth.js";
    import { testExecutionTools } from "./test-execution.js";
    import { testResultsTools } from "./test-results.js";
    import { groupsTools } from "./groups.js";
    import { environmentTools } from "./environment.js";
    import { packagesTools } from "./packages.js";
    import { configTools } from "./config.js";
    import { utilitiesTools } from "./utilities.js";
    
    export const allTools = {
      ...authTools,
  • src/server.ts:8-44 (registration)
    Imports allTools and uses it to dispatch tool calls in the MCP server request handler, retrieving the specific tool by name and executing its handler.
    import { allTools, ToolName } from "./tools/index.js";
    import { detectQitCli, getQitCliNotFoundError } from "./cli/detector.js";
    
    export function createServer() {
      const server = new Server(
        {
          name: "qit-mcp",
          version: "0.1.0",
        },
        {
          capabilities: {
            tools: {},
          },
        }
      );
    
      // List available tools
      server.setRequestHandler(ListToolsRequestSchema, async () => {
        // Check if QIT CLI is available
        const cliInfo = detectQitCli();
    
        const tools = Object.entries(allTools).map(([_, tool]) => ({
          name: tool.name,
          description: cliInfo
            ? tool.description
            : `${tool.description}\n\n⚠️ QIT CLI not detected. ${getQitCliNotFoundError()}`,
          inputSchema: zodToJsonSchema(tool.inputSchema),
        }));
    
        return { tools };
      });
    
      // Handle tool calls
      server.setRequestHandler(CallToolRequestSchema, async (request) => {
        const { name, arguments: args } = request.params;
    
        const tool = allTools[name as ToolName];
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 discloses that the tool checks and shows authentication status, but fails to describe key behavioral traits: what the output looks like (e.g., success/failure, user details), whether it has side effects (likely none, but not stated), or any error handling. The CLI installation note is context but not core behavior. This leaves significant gaps for a tool with no 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.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is poorly structured and not concise. The first sentence states the purpose clearly, but the rest is an error message about CLI installation that doesn't belong in the tool description—it should be handled elsewhere (e.g., in error responses or documentation). This adds unnecessary length and distracts from the core functionality, reducing clarity and efficiency.

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 tool's simplicity (0 parameters, no annotations, no output schema), the description is incomplete. It lacks details on output format (e.g., what 'show current authentication status' entails), error conditions, or dependencies. The CLI installation note is misplaced and doesn't compensate for these gaps, making it inadequate for effective agent use despite the low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100% (as there are no parameters to describe). The description doesn't need to add parameter semantics, so a baseline score of 4 is appropriate. It correctly doesn't mention any parameters, aligning with the empty input schema.

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 tool's purpose: 'Check if QIT CLI is authenticated and show current authentication status.' This specifies the verb ('check' and 'show') and resource ('authentication status'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'authenticate' beyond the read-only nature implied by 'check' and 'show'.

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?

The description implies usage by stating the tool checks authentication status, which suggests it should be used to verify authentication before operations that require it. However, it lacks explicit guidance on when to use this tool versus alternatives like 'authenticate' (for logging in) or other status-checking tools, and doesn't specify prerequisites or exclusions beyond the CLI installation note.

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/woocommerce/qit-mcp'

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