Skip to main content
Glama
TheQtCompanyRnD

squish-mcp

Official

run_test

Execute a Squish test suite or a single test case using the absolute path and optional context variables, returning test results.

Instructions

Run a Squish test suite or test case.

You need to figure out the test suite and test case absolute paths on your own. You may be asked to either run a full test suite or a single test case within a test suite.

This is a wrapper around the squishrunner command line tool.

IMPORTANT PATH HANDLING AND SQUISH TEST NAMING CONVENTIONS:

  • All paths are absolute paths, but you should infer missing ones from context.

  • Test suites are named like suite_<test_suite_name> - these are folders under the root path

  • Test cases are named like tst_<test_name> - these are folders under the test suite path

  • Test files are under the test case folders and are named like test.py

Args: test_suite_path: Absolute path to the test suite which you should figure out on your own Example: "/Users/yourname/projects/addressbook/suite_py" context: Dictionary variables of options to pass to Squish Format: {"VAR_NAME": "value"} test_case_name: Name of the test case to run. Example: "tst_general"

Returns: Test run results with squishrunner output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextYes
test_case_nameNo
test_suite_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stderrYesStandard error output from squishrunner
stdoutYesStandard output from squishrunner
Behavior3/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 it is a wrapper around squishrunner, requires absolute paths, and returns test results, but does not discuss side effects, error handling, or performance characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is well-structured with sections for purpose, path handling, args, and returns. It is slightly verbose but every sentence adds necessary context for a complex tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and the presence of an output schema, the description covers the essential aspects: purpose, parameter usage, and return value. Minor gaps include missing details on prerequisites and error scenarios.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining each parameter (test_suite_path, context, test_case_name) with examples and format details, adding significant value beyond the bare schema.

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

Purpose5/5

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

The description clearly states the tool runs a Squish test suite or test case, with a specific verb and resource. It distinguishes from sibling tools (analyze_, create_, etc.) by focusing on execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains that paths must be inferred and provides naming conventions, implying when to use the tool. However, it does not explicitly exclude alternative tools or specify when not to use it.

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/TheQtCompanyRnD/squish-mcp'

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