Skip to main content
Glama

get_qit_dir

Retrieve the QIT configuration directory path to access testing tools for WordPress/WooCommerce plugins.

Instructions

Get the QIT configuration directory path.

⚠️ 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 for the 'get_qit_dir' tool. It executes the QIT CLI command 'qit:dir' using the executeAndFormat utility to retrieve the QIT configuration directory path.
    handler: async () => {
      const cmdArgs = ["qit:dir"];
      return executeAndFormat(cmdArgs);
    },
  • Input schema for 'get_qit_dir' tool, which takes no parameters.
    inputSchema: z.object({}),
  • The tool registration object defining 'get_qit_dir' within utilitiesTools, which is later aggregated into allTools.
    get_qit_dir: {
      name: "get_qit_dir",
      description: "Get the QIT configuration directory path.",
      inputSchema: z.object({}),
      handler: async () => {
        const cmdArgs = ["qit:dir"];
        return executeAndFormat(cmdArgs);
      },
    },
  • Registration of utilitiesTools (containing get_qit_dir) into the allTools aggregate export used by the server.
    ...utilitiesTools,
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 requires QIT CLI installation and may fail if not detected, which is useful behavioral context. However, it lacks details on what the tool returns (e.g., a string path, error codes), performance characteristics, or side effects, leaving 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 verbose. The first sentence states the purpose clearly, but the rest is dominated by installation instructions and error messages that don't belong in a tool description. This wastes space and dilutes the core information, making it less effective for an AI agent.

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 no annotations and no output schema, the description is incomplete. It explains prerequisites but fails to describe the return value (e.g., what the path looks like, error formats) or behavioral nuances. For a tool with zero structured data, this leaves the agent under-informed about how to interpret results.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose and prerequisites. This meets the baseline for tools with no parameters.

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: 'Get the QIT configuration directory path.' This is a specific verb ('Get') and resource ('QIT configuration directory path'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'manage_config' or 'list_environments', which might also involve configuration or environment paths.

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 focuses entirely on installation prerequisites and error handling for missing CLI, without mentioning context, prerequisites beyond CLI installation, or comparisons to sibling tools like 'manage_config' that might handle configuration differently.

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